-
Notifications
You must be signed in to change notification settings - Fork 234
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 failure: CommandLine Error: Option 'spirv-text' registered more than once! #519
Comments
Passing
|
Strange… On Arch it builds and works fine with the LLVM 13 stack, excepted we have to set |
@tgurr everything in your compute stack needs to use the same LLVM and SPIRV versions, otherwise you get that kind of mismatch issues. See last comments in: intel/intel-graphics-compiler#224 You need to build both opencl-clang and llvm-spirv yourself, or take them both from the system, not mix them. |
@tgurr sorry for the late response, it took me a while to get a new release to actually build and work, so what I found out is that as soon as I built igc with vc-intrinsics support by either checking out and building vc-intrinsics in-place with igc or having it packaged separately and passing I do use prebuilds from system for the mentioned packages (which are all built against the same LLVM version), see:
Looks like Gentoo is also running into a similar or the same issue as they disable VC as well: NixOS was also running into it according to a comment by @calbrecht at NixOS/nixpkgs#169729 (comment) however I can't find any reference on how they solved the issue. |
So far, I've seen "registered more than once" errors only when even one component in the whole stack used mismatching LLVM version at build time. Although you've tried to make sure that build uses only single LLVM version, do you other LLVM version(s) installed on your system? (To make sure your builds are really avoiding wrong LLVM versions, it may be best to do a test build in a container which has nothing else than components built by the same LLVM installed. If that does not work, then we can be sure it's not LLVM mismatch.) Btw. Based on this: https://github.com/intel/intel-graphics-compiler/projects?type=classic IGC production testing is still done against LLVM 11, with LLVM 14 being next one to be production supported, and LLVM 12 + 13 having just beta support. While I can build compute stack (with VC) fine with LLVM 12, compute-runtime tests fail with LLVM 13 on Ubuntu 22.04: #553 So LLVM 13 might be an issue too. |
I do not have any other LLVM versions on the system, everything is handled by the package manager and nothing is/was installed manually. Exherbo is a source-based distribution like Gentoo so I can be quite sure about this. I'll migrate our packages to LLVM 14 as soon as we've packaged that, currently LLVM 13.0.1 is the latest we've packaged to date. I'll report back if the situation improved with LLVM 14 and also monitor the Gentoo progress on intel/intel-graphics-compiler#236. |
@tgurr that particular issue was related to a |
@calbrecht huge thanks for that hint! We actually still built |
Maybe this is related to IGC docs already stating that static version LLVM-SPIRV-Tools is not supported: intel/intel-graphics-compiler@205e9c3 ? (See also the linked ticket in the Khronos SPIRV project.) |
We previously already built |
I compile graphics compiler intel/intel-graphics-compiler#263 (comment) but I face the
probably compiler is in broken state, but out of the scope, entire project architecture is madness, broken binary interface for welcome... |
I'm running into the following build failure:
compute-runtime version I'm trying to build:
Installed dependencies:
Complete build log:
intel-compute-runtime-22.09.22577.log
The text was updated successfully, but these errors were encountered: