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

Don't crash in MatmulLoopPipeline in the presence of an early return. #3393

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

jlebar
Copy link
Collaborator

@jlebar jlebar commented Mar 15, 2024

Don't crash in MatmulLoopPipeline in the presence of an early return.

PR chain

  1. 👉 Don't crash in MatmulLoopPipeline in the presence of an early return. #3393 👈 YOU ARE HERE

Found in an internal OAI workload, early returns were causing a crash in
MatmulLoopPipeline because getBackwardSlice was trying to iterate out of
a tt.function op!  That is not going to work.  :)

GPC: pipeline-crash
@jlebar jlebar requested a review from ptillet as a code owner March 15, 2024 20:51
@jlebar
Copy link
Collaborator Author

jlebar commented Mar 15, 2024

Thank you!

@jlebar jlebar enabled auto-merge (squash) March 15, 2024 20:57
@jlebar jlebar disabled auto-merge March 15, 2024 21:00
@jlebar jlebar enabled auto-merge (squash) March 15, 2024 21:00
@jlebar jlebar merged commit 166de9a into main Mar 15, 2024
5 checks passed
@jlebar jlebar deleted the dev-jlebar/pipeline-crash branch March 15, 2024 21:00
karupayun pushed a commit to openxla/triton that referenced this pull request Apr 3, 2024
…triton-lang#3393)

Don't crash in MatmulLoopPipeline in the presence of an early return.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants