← Back to events
ActiveAIRelease

viable/strict/1789454551: [_native][2/8] Add shared CuTeDSL and reduction machinery (#195050)

What happened

Human Notes: Shared infrastructure we'll build on for the rest of the stack How we define an operator in a reasonably general manner -- per-element transforms, reduction specifics, etc. How we will launch a given generated kernel, wrap read-only inputs, etc. How to query the launch device and derive useful quantities for the eventual kernel definitions/launches. Centralise all of this logic and re-use for everything…

Summary assembled by rule from the sources below

Why it's spreading

Sources