Skip to content

[Backend] Bump to llvm/llvm-project@7ec6f1771114#10289

Closed
antiagainst wants to merge 6 commits into
triton-lang:mainfrom
antiagainst:lei/update-llvm-0511
Closed

[Backend] Bump to llvm/llvm-project@7ec6f1771114#10289
antiagainst wants to merge 6 commits into
triton-lang:mainfrom
antiagainst:lei/update-llvm-0511

Conversation

@antiagainst

Copy link
Copy Markdown
Member

@antiagainst
antiagainst marked this pull request as ready for review May 16, 2026 16:03
@antiagainst
antiagainst force-pushed the lei/update-llvm-0511 branch 2 times, most recently from 123835a to 8560fb0 Compare May 30, 2026 05:27
@antiagainst
antiagainst force-pushed the lei/update-llvm-0511 branch from 8560fb0 to fc74468 Compare May 30, 2026 05:52
@neildhar

Copy link
Copy Markdown
Collaborator

Sorry if the checksum validation is causing problems. I set up the LLVM build job to dump the SHA for each build right before uploading (e.g. https://github.com/triton-lang/triton/actions/runs/26669029128/job/78608320883#step:15:21). I found that pointing codex to that build job was pretty good at fetching and updating the correct checksums.

@antiagainst

Copy link
Copy Markdown
Member Author

Sorry if the checksum validation is causing problems. I set up the LLVM build job to dump the SHA for each build right before uploading (e.g. https://github.com/triton-lang/triton/actions/runs/26669029128/job/78608320883#step:15:21). I found that pointing codex to that build job was pretty good at fetching and updating the correct checksums.

Thanks for the pointers! I intially thought it's sha256sum from https://github.com/triton-lang/triton/actions/runs/26669029128. Turns out indeed they are different. Would be convenient if we can aggregate and display at the summary page.

@antiagainst antiagainst closed this Jun 5, 2026
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