-
Notifications
You must be signed in to change notification settings - Fork 164
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
SPIRVModuleReport include guarded but usage is not #353
Comments
Which version of headers and tools the system has? (Release notes list with which versions they've been built with) |
|
Ok, Used SPIRV-* versions from end of 2023, whereas your versions were from mid 2024. I think that should be fine. Could you do build with additional PS. Does latest IGC v1.x build fine in the same setup i.e. is this regression? |
I move to 2.5.6 and the error still occurs. Here's a full log with |
And now I got even more errors
|
I wonder whether IGC is actually finding those prebuilt SPIRV components correctly, as I've never seen such messages. I've never tried using system versions for those projects though, only for rest of the deps... (And I been bulding IGC v1, as my IGC v2 tries have failed due to LLVM-Translator issue, but you're not getting even that far.) As SPIRV-Headers & SPIRV-Tools are rather small projects, what if you'll just skip telling IGC to use pre-built versions and get their sources to same dir where the IGC repo dir is (and where it searches for them with these names)?
PS. I'm not IGC maintainer, just somebody who's been building its latest versions occasionally on Ubuntu, for past few years. |
I fixed the previously posted compilation by having SPIRV-LLVM-Translator download its own SPIRV headers (removed But the original issue remains
|
Found the issue! |
Ah, that explains why I was not seeing your errors. I was using just Help line in CMake |
Hi,
The compilation of the v2.1.12 fails on Alpinelinux 1 with the following error
Both
SPIRV-Headers
andSPIRV-Tools
are taken from the systemThe text was updated successfully, but these errors were encountered: