-
Notifications
You must be signed in to change notification settings - Fork 229
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 error error: undefined reference to `_Z18__spirv_ImageWritePU3AS133__spirv_Image__void_2_0_0_0_0_0_1Dv4_iDv4_ji' #704
Comments
Hi @pvelesko Could you try with IGC as of https://github.com/intel/intel-graphics-compiler/releases/tag/igc-1.0.15770.11 ? |
Not sure if this is related, but I'm getting very similar errors in Arch Linux since version 23.52.28202.14. Version 24.05.28454.6 + IGC 1.0.15985.7 also gives me the same result in when building:
There are other similar errors following it in the compilation, like these:
|
@JablonskiMateusz Any update on this? I tried using latest neo 24.09.28717.12 with igc 1.0.16238.4, and the problem still persists. Both neo and igc are built with the listed dependency commits from their release description. |
I got the same issue too, any solutions for this issue? |
Same issue here in Arch Linux with Version 24.09.28717.12 + ICG 1.0.16510.1 |
@dbermond I was able to fix the compile issues on Arch Linux updating all PKGBUILD for IGC + dependencies, changes are available here: https://github.com/vidalinux/AUR: |
The error message says directly that this is failure on compiler backend side.
Please attach reproducer and create an issue in IGC repo |
@vidalinux I have not compiled/tested your setup, but currently it's not suitable because you are using different dependency versions for IGC in comparison to the ones specified by upstream. Although this may compile, it can have silent segmentation fault issues that are shown only at runtime, since IGC seems to be sensible to these versions. This have already happened in the past when we used binary dependencies. Also, your spirv-tools is 2024.1, which is ahead of the one shipped in the official repositories. We have switched to using a source-based build for most IGC dependencies exactly for, among other things, avoid the problems described above, making sure that we are using dependencies that are tested by upstream, and the current intention is to stick with this type of build. This also helped a lot with building issues in IGC when we were using a binary (prebuild) llvm at a different version. For using your setup, we would need a spirv-llvm-translator15 (and so on) in the official repositories, and we are avoiding this by using a source-based build. |
@JablonskiMateusz Thank you for the reply. I have opened an issue in the IGC repository. |
@dbermond @JablonskiMateusz an issue has been open on igc for a while. |
It works fine for me when using |
neo-error.txt
Tried with building LLVM standalone and also with LLVM getting built alongside neo.
The text was updated successfully, but these errors were encountered: