You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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?
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
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
The text was updated successfully, but these errors were encountered: