-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Inductor Cutlass backend] Enabling flexible EVT-based pointwise fusions with additional tensor input #113959
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ons with additional tensor input This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
This was referenced Nov 17, 2023
This was referenced Nov 17, 2023
kadeng
added a commit
that referenced
this pull request
Nov 17, 2023
…ons with additional tensor input This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI ghstack-source-id: 308200852b2127ea42905cd80a93d0646de7ec65 Pull Request resolved: #113959
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
kadeng
added a commit
that referenced
this pull request
Nov 17, 2023
…ons with additional tensor input This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI ghstack-source-id: 74e3a9006f001022f4437ed02e21180e803e3f01 Pull Request resolved: #113959
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
kadeng
added a commit
that referenced
this pull request
Nov 17, 2023
…ons with additional tensor input This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI ghstack-source-id: 5b43ae9f8ef932686506b536df1ae89a5589b6c2 Pull Request resolved: #113959
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
This was referenced Nov 21, 2023
This was referenced Nov 28, 2023
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
This was referenced Dec 5, 2023
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
This was referenced Dec 12, 2023
Closed
…ntwise fusions with additional tensor input" This diff enables flexible EVT based Matmul fusions which may require one tensor input in addition to the Matmul operands ( A and B ). Test Plan: * Additional unit tests in test/inductor/test_max_autotune.py * Manual inspection of the generated code * CI [ghstack-poisoned]
Moved to a (draft) feature branch, see #115919 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
This diff enables flexible EVT based Matmul fusions which may require one tensor input
in addition to the Matmul operands ( A and B ).
Test Plan: