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

Add automated releases for llvm branches #537

Closed
ZzEeKkAa opened this issue Jun 21, 2024 · 2 comments · Fixed by #551
Closed

Add automated releases for llvm branches #537

ZzEeKkAa opened this issue Jun 21, 2024 · 2 comments · Fixed by #551

Comments

@ZzEeKkAa
Copy link
Contributor

Hello there!
I see that patches are being backported to to the older llvm branches, but never being released. Is it okay to add automated releases for it? So that different build systems, like conda can references them?

I've done it for spirv-llvm-translator, and it looks like same pattern could be applied to this repository:
KhronosGroup/SPIRV-LLVM-Translator#2586

@wenju-he
Copy link
Contributor

hi @ZzEeKkAa thank you for the suggestion. I think it is a good idea to add automatic release that includes new changes to opencl-clang (although it is not frequent) and link with latest release of llvm and SPIRV-LLVM-Translator.
Do you have bandwidth to work on this?

@th0ma7
Copy link

th0ma7 commented Jul 6, 2024

I second that! Would be great to have this. One note thought is that automated patching using git part of the build process won't work anymore and will need to be adapted. Ref.: #538

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 a pull request may close this issue.

3 participants