Implement multi-output autotuning in Torchinductor - #105
Conversation
Add support for multi-output autotuning in Torchinductor, allowing templates and extern kernels to share the same operator contract without additional copy operations. This change includes updates to choice construction, benchmarking, and IR generation to handle multiple outputs seamlessly.
|
Hi @edderstack! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
|
@edderstack have you looked into the Subgraph Decomposition autotuning ? this can handle arbitrary, multiple operations and outputs. |
Add support for multi-output autotuning in Torchinductor, allowing templates and extern kernels to share the same operator contract without additional copy operations. This change includes updates to choice construction, benchmarking, and IR generation to handle multiple outputs seamlessly.