Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle the compilation step for end users. #14

Open
101001000 opened this issue Dec 31, 2022 · 0 comments
Open

How to handle the compilation step for end users. #14

101001000 opened this issue Dec 31, 2022 · 0 comments

Comments

@101001000
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant