windows-gnu: Failed to load codegen backend: LoadLibraryExw failed: The specified procedure could not be found. (os error 127)
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behaviour
Build script using spirv-builder runs without errors
Example & Steps To Reproduce
- Copy
rust-toolchain.tomlto use rustc nightly-2025-06-23 - build-dependency
spirv-builder = { git = "https://github.com/Rust-GPU/rust-gpu" } cargo build
The build fails with the full error:
error: couldn't load codegen backend \\?\C:\Users\****\Downloads\fvm2d\target\debug\deps\rustc_codegen_spirv.dll: LoadLibraryExW failed: The specified procedure could not be found. (os error 127) (The specified procedure could not be found. (os error 127)) (retried 5 times)
rustc_codegen_spirv.dll does exist in that location, but the error suggests that some symbol is missing that is attempting to be loaded. I don't know how to get the name of the procedure it wants.
System Info
- Rust: rustc 1.89.0-nightly (be19eda0d 2025-06-22) (the date on this value always seems to be 1 day behind the version specified in
rust-toolchain.toml) - OS: Win11
- GPU: NVIDIA GeForce MX450
- SPIR-V: SPIRV-Tools v2025.2 unknown hash, 2025-05-06T12:14:19+00:00
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the nightly version in rust-toolchain.toml, the git spirv-builder dependency, and cargo build on Windows 11. Investigate why rustc_codegen_spirv.dll cannot be loaded and verify that the same build script completes without the LoadLibraryExW error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, compilers, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100