-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Build with SYCL fails using intel/llvm compiler #2035
Comments
Observation is that build succeeds if |
This looks like an issue with SYCL compiler headers or the way SYCL compiler is built. oneDNN code happily compiles with Intel DPC++/C++ Compiler 2024.x and open source nightly-20230801. |
I used more recent intel/llvm compiler (intel/llvm@3b91b0b. it's first included in nightly-2024-08-10). Also note that I see same issue on https://github.com/intel/llvm/tree/sycl-rel_5_2_0 branch. Also, oneDNN builds fine with intel/llvm if it's used for all build targets. But as soon as you are using different host compiler, you see this issue. |
I realize that you have issues with recent builds of intel/llvm and I can reproduce it. My point is that compiler barks at it's own headers, so the issue is likely on the compiler side or in the environment. |
Changes: * Added a hack to fix 2035 in oneDNN * Commented out oneapi specific location for libOpenCL.so * Added hacks in torch-xpu-ops to WA dpc++ and intel/llvm behavior differences Above are hacks which need proper resolutions. See: oneapi-src/oneDNN#2035 Requires: intel/torch-xpu-ops#635 Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
Reported intel/llvm#15120 |
With:
Build fails if configured in the following way (that's pytorch style build, see https://github.com/pytorch/pytorch/blob/a9d34138dfd5c049305487fc9f1b8bae0cadc98e/cmake/Modules/FindMKLDNN.cmake#L48):
Note: icx/icpx are symbolic links to
clang-19
built in intel/llvm.Few files fail with the similar error. For example:
For individual file this issue can be reproduced with:
The text was updated successfully, but these errors were encountered: