[Pkg-opencl-devel] Bug#1004883: intel-graphics-compiler: switch to llvm-toolchain-13

[Andreas Beckmann]

Control: forwarded -1 
https://github.com/intel/intel-graphics-compiler/issues/227

On 02/02/2022 22.43, Sebastian Ramacher wrote:
> Source: intel-graphics-compiler
> Version: 1.0.8744-2

> The current default version of llvm is llvm-toolchain-13. To reduce the
> number of llvm versions, please consider switchting to llvm-toolchain-13
> (or the unversioned counterpart).

Switching to llvm-13 seems to be easy, at least after upgrading to the 
latest upstream release. It builds. Unfortunately building 
intel-compute-runtime against intel-graphics-compiler built with llvm-13 
causes errors:
https://github.com/intel/intel-graphics-compiler/issues/227
while the same works fine if built against llvm-11 (and maybe llvm-12 
with some patching).

Upstream Status:

LLVM 11 Support: Production
https://github.com/intel/intel-graphics-compiler/projects/1

LLVM 12 Support: Beta
https://github.com/intel/intel-graphics-compiler/projects/2

LLVM 13 Support: Experimental
https://github.com/intel/intel-graphics-compiler/projects/3

So for now using llvm-11 to build intel-graphics-compiler seems to be 
the best solution to get intel-compute-runtime working again.

In order to build intel-graphics-compiler against llvm-11 we would need 
to reintroduce spirv-llvm-translator and intel-opencl-clang built 
against llvm-11. These are tightly coupled to the llvm version being 
used and will change the soname accordingly. I would therefore 
reintroduce them as new source packages with '-11' appended.
Would adding two more source packages depending on llvm-11 be OK?
That's the only solution I see for making intel-compute-runtime 
buildable again on a short time frame.


Andreas

PS: The insane setup that we currently have: building 
intel-graphics-compiler with llvm-12 or llvm-11 while using 
intel-opencl-clang built with llvm-13 does not work. And nobody is going 
to debug that.