Skip to content
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
wants to merge 21 commits into from

Conversation

kadeng
Copy link
Contributor

@kadeng kadeng commented Nov 17, 2023

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:

  • Additional unit tests in test/inductor/test_max_autotune.py
  • Manual inspection of the generated code
  • CI

…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]
Copy link

pytorch-bot bot commented Nov 17, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/113959

Note: Links to docs will display an error until the docs builds have been completed.

❌ 14 New Failures, 12 Unrelated Failures

As of commit ba6150c with merge base afe6d27 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

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]
…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]
…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]
@kadeng
Copy link
Contributor Author

kadeng commented Dec 15, 2023

Moved to a (draft) feature branch, see #115919

@kadeng kadeng closed this Dec 15, 2023
@facebook-github-bot facebook-github-bot deleted the gh/kadeng/29/head branch January 14, 2024 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant