Hi developers,
When using cloc 0.9 (which is based on llvm 3.2), one of the example, in AMD APP SDK, MonteCarloAsianDP_Kernels.cl can work.
However, when the new LLVM toolchain uses the addrspacecast to generate the kernel code, CLOC emits the error message like error: addrspacecast not implemented.
For now, I can still use cloc -hsail MonteCarloAsianDP_Kernels.cl to use the old version (hlc3.2) of LLVM toolchain to run my application. This issue can also be found in the current LLVM trunk.
So, how to work around this kind of problem when using new CLOC toolchain now? There are some benchmarks that fail to compile. [EDIT: I think a viable solution may be trying to not use generic address space in this case.]
Thanks.
The aforementioned example is in the attachment.
Kernel code
LLVM Assembly code
Hi developers,
When using cloc 0.9 (which is based on llvm 3.2), one of the example, in AMD APP SDK, MonteCarloAsianDP_Kernels.cl can work.
However, when the new LLVM toolchain uses the
addrspacecastto generate the kernel code, CLOC emits the error message likeerror: addrspacecast not implemented.For now, I can still use
cloc -hsail MonteCarloAsianDP_Kernels.clto use the old version (hlc3.2) of LLVM toolchain to run my application. This issue can also be found in the current LLVM trunk.So, how to work around this kind of problem when using new CLOC toolchain now? There are some benchmarks that fail to compile. [EDIT: I think a viable solution may be trying to not use
genericaddress space in this case.]Thanks.
The aforementioned example is in the attachment.
Kernel code
LLVM Assembly code