-
Notifications
You must be signed in to change notification settings - Fork 643
oneAPI: Bump NEO to v25.27.34303.5 #11720
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
Conversation
|
@maleadt |
|
intel/compute-runtime#838 Issue created. I think there's a device ID mismatch, although I think I used the recommended versions for the stack. |
Presumably, according to upstream it may be related to our build. Which isn't unthinkable... |
|
But I'd hope @michel2323 isn't using a system with C++03 ABI |
|
Calling compiled with GCC 11 as committed right now. From outside the container: No crash of From inside the container (as here in buildkite): Segfault. Tried using GCC 14. There I don't have to even pass arguments. Outside container: Inside the container: glibc mismatch. How should I proceed here @maleadt @giordano ? I have to use GCC 11 due to C++20 features they use. I am not sure I want to backport that. |
|
The glibc error when using GCC 14 is weird; @giordano I take it our CSL is too outdated to handle GCC 14 binaries? It's probably not common that a recipe executes binaries during the build, but we have to, and NEO does not support musl (so we can't bootstrap). Simply bumping GCC is not going to help because even the GCC 11 binaries crash within the container while they work outside. I guess that bumping glibc would work; can we do that by installing Glibc_jll.jl? |
|
Updating the compiler libraries in the RootFS is what I was trying to do in JuliaPackaging/BinaryBuilderBase.jl#423, but got stuck with musl/glibc madness. |
|
@michel2323 Can you try reverting to GCC 11 while replacing the |
|
I've started to play with it, but got stuck. Changing libc seems more involved than changing |
|
@maleadt I don't know why one segfaults and the other not. I've installed On my system, In the container it fails: I've checked |
| # Need C++20 | ||
| CMAKE_FLAGS+=(-DCMAKE_CXX_STANDARD=20) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also sounds like a patch for upstream. Downstream packagers should never set the C++ standard, that's the developers' business.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is actually set here: https://github.com/intel/compute-runtime/blob/d0fdeb0339afaa6db37411e10c41f291945aa727/CMakeLists.txt#L323 . So I'm a bit confused. I definitely get an error without explicitly setting it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is indeed confusing 😕
|
@maleadt @giordano Again some interesting developments. I still get the segfault, no matter what libc and libstdc++ I use. However, upon further investigation, it seems that ocloc compiles successfully. It crashes when exiting. I'm starting to believe that this is a legitimate segfault, and that this system catches it. |
|
|
|
That's really annoying... Thanks for looking into it though. If we do end up with the required files, I guess the workaround is fine as we never use |
No description provided.