-
Notifications
You must be signed in to change notification settings - Fork 52
Rust-gpu main fails to build #242
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
Comments
This comment has been minimized.
This comment has been minimized.
I am getting a panic here:
|
This comment has been minimized.
This comment has been minimized.
Ok, looks like updating the lockfile causes issues: https://github.com/Rust-GPU/rust-gpu/actions/runs/14645774261/job/41099428403?pr=243 So it is in one of those. |
This was probably caused by libm releasing 0.2.13 2 days ago. Can't find the issue right now, will look later if someone hasn't beaten me to it. |
Yeah, if force libm to 0.2.11 this error disappears. Check out https://github.com/simensgreen/rust_gpu_union_issue/tree/libm-fixed |
Ok, so something about our symbol resolution when swapping out libm intrinsics is messing up with the new versions. |
I don't have time to bisect, but a good candidate is rust-lang/compiler-builtins@161036a. My hunch is because these are inlined, we can't replace the symbol because the symbol doesn't exist because they're inlined. |
To work around this for now you can use patch in your Cargo.toml for crates.io to set libm for all deps. |
Coming here from the libm side. is this crate looking for global symbols from a libm rlib? If so this isn't reliable, we don't provide |
Ok thanks. I am unfamiliar with this portion of the project so I'll take a this week if someone doesn't get to it before me, thanks for chiming in. |
Just an update on this, we landed a temporary fix to lock |
Do you happen to know what this error actually prints? Might narrow things down. There is also a chance this is related to f16 or f128 if those aren't well supported in the cg backend yet. As of very recently, the backends can say whether or not they support them rust-lang/rust#140323, I'll be switching libm and compiler-builtins to use this after the beta branch and bootstrap bump (~2 weeks). |
We're on an old version of rustc that doesn't include those changes I think (nightly-2024-11-22). I'll get the messages later today. Thanks for following up! |
Expected Behaviour
Successful compilation
Example & Steps To Reproduce
cargo build
System Info
Backtrace
Backtrace
The text was updated successfully, but these errors were encountered: