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

Next-generation Intel compilers are not recognized by default #537

Open
Pennycook opened this issue Jul 21, 2023 · 3 comments
Open

Next-generation Intel compilers are not recognized by default #537

Pennycook opened this issue Jul 21, 2023 · 3 comments

Comments

@Pennycook
Copy link

Support for the classic Intel compilers (icc and icpc) was previously added in response to #136.

The next-generation compilers (icx and icpx) are currently not recognized by default, and it took me a while to figure out what was happening here. Bear does recognize icpx in -fsycl mode (because it resolves to clang), so for mixed C++/SYCL projects only some of the files end up missing from the compilation database.

I was able to work around this by adding icx and icpx to the compilers_to_recognize field of a configuration file, but it would be great if these could be added as officially recognized compilers (like nvcc).

@rizsotto
Copy link
Owner

Hi Pennycook, I think the icc was recognized by the 2.x version. In the 3.x version it was not carried over.

Since I am not into C++ that much recently, could you help me to send me link to these tools' page?

@Pennycook
Copy link
Author

Pennycook commented Jul 24, 2023

Thanks for taking a look at this so quickly.

I believe the best way to get icx and icpx is from https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html. There are a few different options there (direct download, apt repository, Docker container, etc).

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

2 participants