-
-
Notifications
You must be signed in to change notification settings - Fork 302
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
Comments
Hi Pennycook, I think the Since I am not into C++ that much recently, could you help me to send me link to these tools' page? |
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). |
Support for the classic Intel compilers (
icc
andicpc
) was previously added in response to #136.The next-generation compilers (
icx
andicpx
) are currently not recognized by default, and it took me a while to figure out what was happening here. Bear does recognizeicpx
in-fsycl
mode (because it resolves toclang
), 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
andicpx
to thecompilers_to_recognize
field of a configuration file, but it would be great if these could be added as officially recognized compilers (likenvcc
).The text was updated successfully, but these errors were encountered: