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
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).
The text was updated successfully, but these errors were encountered:
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: