[Libclc-dev] Can't compile Libclc anylonger with current git LLVM since 16. Mai
Dieter Nützel via Libclc-dev
libclc-dev at lists.llvm.org
Sat May 28 16:52:49 PDT 2016
Am 29.05.2016 00:55, schrieb Jan Vesely:
> This failure is not caused by libclc, but rather change in clang
> (r269670). The revision changed the way clc extensions are handled and
> did not allow any extensions for nvptx.
> compilation fails because libclc configure sets -Dcl_khr_fp64, but
> clang refuses to enable the extension.
> Possible fixes/workarounds:
> 1.) Don't compile nvptx libclc target. amd targets have relied on clang
> providing device information for some time, and should be fine (the bug
> in current clang should not be fatal).
> 2.) Remove -Dcl_khr_fp64 from nvptx targets in configure. We'll
> probably need to that anyway. This might lead to miscompiled libclc for
> nvptx and you'll see a ton of warnings.
> 3.) Apply patches [0,1,2,3] to your clang and recompile. Patch 
> should be enough, but I haven't tested them individually.
>  http://reviews.llvm.org/D20447
>  http://reviews.llvm.org/D20744
>  http://reviews.llvm.org/D20388
>  http://reviews.llvm.org/D20389
> On Sun, 2016-05-29 at 00:29 +0200, Dieter Nützel via Libclc-dev wrote:
>> Hello to the list,
>> my last and running Libclc was compiled with git LLVM taken from the
>> same day:
Thank you very much Jan!
I've taken route 2.) and libclc is running as before, e.g. on AMD
Awaiting route 3.), next.
Let me know when clang patches are landed.
More information about the Libclc-dev