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
Intel provides a oneAPI compiler installation which could reduce friction on the installation for render users. Codeplay also provides a plugin for that installation to work with CUDA.
This compiler is the LLVM SCYL implementation I'm using right now, but with some proprietary Intel features, so maybe it's possible to use it instead distributing Clang directly.
That been said, after some preliminary tests, I wasn't able to compile Boost::log with icx neither with dpcpp by using only the -fsycl tag.
By using the flag -fsycl-targets=nvptx64-nvidia-cuda, I get an error of not being able to generate LLVM bytecode for that target because proprietary optimizations are enabled
I'm writing this issue for remembering the future me about this when I try to pack the first release.
The text was updated successfully, but these errors were encountered:
Intel provides a oneAPI compiler installation which could reduce friction on the installation for render users. Codeplay also provides a plugin for that installation to work with CUDA.
https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html#dpcpp-cpp
This compiler is the LLVM SCYL implementation I'm using right now, but with some proprietary Intel features, so maybe it's possible to use it instead distributing Clang directly.
That been said, after some preliminary tests, I wasn't able to compile Boost::log with icx neither with dpcpp by using only the -fsycl tag.
By using the flag -fsycl-targets=nvptx64-nvidia-cuda, I get an error of not being able to generate LLVM bytecode for that target because proprietary optimizations are enabled
I'm writing this issue for remembering the future me about this when I try to pack the first release.
The text was updated successfully, but these errors were encountered: