trunk/3e9e74c046a7e412d4488fb55f714db24b4e3d9a: [_native][2/8] Add shared CuTeDSL and reduction machinery (#195050)
- PyTorch: 960 events in the last 90 days
- PyTorch: 949th Release in the last 90 days
- Previous: earlier the same day · trunk/b539f7a9316da263d943983cde4c5d149635a7eb: [CI] Move CUDA 13.0 jobs from pull/trunk to periodic (#197031)
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