trunk/199499c48eb5f76febc1fb3dd5c59a6facfd449b: Use vectorized kernels for index_copy (#201814)
- PyTorch: 2744 events in the last 90 days
- PyTorch: 2701th Release in the last 90 days
- Previous: earlier the same day · trunk/39924e1b420c4cfcd1f648be2c18f90377122a3f
What happened
Linked issue or supporting maintainer Supported by @ngimel BC-breaking? No. Summary (human written only) Use vectorized kernel for scatter and index_copy ops, redispatch index_copy to scatter when profitable Cap the number of blocks because that leads to better perf (revisit later to maybe use CLC) Agent details (AI-generated) Authored with assistance from Codex. Adds a copy specialization to the existing native vec…
Summary assembled by rule from the sources below