llvmPackages_{20,21}.libclc: reenable#436446
Conversation
|
|
Evaling as broken should be fine. |
|
Closing in favor of #407738 |
|
Just because we're not ready to update the default yet doesn't mean we have to wait to have working libclc… |
|
Might've jumped the gun there ^^' |
49ee4fe to
98b13bf
Compare
There was a problem hiding this comment.
This seemed like a typo to me, it caused buildInputs to eval as [..., [...]]. Kinda surprised that mkDerivation didn't complain about that
98b13bf to
378d3d4
Compare
378d3d4 to
39bd105
Compare
|
Don't we need to update the version check introduced in #429382? |
|
Do you mean lib.versionAtLeast metadata.release_version "16" && lib.versionOlder metadata.release_version "20"Right now I updated it to go up to version 21 only, as there's no version of |
|
Thanks! |
#429382 dropped the
libclcattribute ofllvmPackagesfor LLVM 20/21 because there was no appropriateSPIRV-LLVM-Translatorversion. #432015 introduced the required versions. This PR reintroduceslibclcand adjusts patches as some were applied upstream.llvmPackages_20.libclcbuilds properly.On LLVM 21 it's broken for now, as
SPIRV-LLVM-Translatorneeds nightly SPIRV Headers (see here). After manually forcingspirv-headersandspirv-toolsonto nightly versions,llvmPackages_21.libclcalso builds properly. Right now, it will evaluate as broken asspirv-llvm-translatoris marked as broken for LLVM 21 with current SPIRV version.#429382 was to fix OfBorg eval issues - is evaling as broken an issue, or only if it fails to eval at all?
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.