-
Notifications
You must be signed in to change notification settings - Fork 83
Bump to triton-lang/triton@dbfbc1e1e6c #363
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
base: main
Are you sure you want to change the base?
Conversation
|
this PR needs triton-lang/triton#8766 merged |
104362e to
2212351
Compare
|
@nhat-nguyen, sorry for the explicit ping but I did not have access to request a formal review. Could you be pleaase review the PR / or request review from appropriate stakeholders? |
|
gently pin |
|
the api changes for op creation and driver.py look good to me. thanks a lot for helping us update this! as for the lit tests, do you know what are the main changes that caused the differences? tangentially, we're not using the triton-to-linalg pass anymore (triton-to-linalg-experimental is the main one now), so it might be cleaner to remove the pass and those tests first before the triton bump so that we don't have to update the lit files. |
In the new llvm version, removing the triton-to-linalg pass helps a lot! 🎉 |
|
already update. |
|
gently pin |
|
ping @bmyerz0 @red1bluelost |
|
i think it would be cleaner if we delete the TritonToLinalg pass in a different PR |
I see. 👌 |
04c7627 to
1c5906e
Compare
|
this pr depends on #366 |
bypass bf16 type update api usage for llvm version change update backend update test case
|
Please see #367 |
This updates to latest Triton main which should resolve the nightly build issues.
Primary changes: