-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
chore: Bump compiler_builtins #124886
chore: Bump compiler_builtins #124886
Conversation
rustbot has assigned @Mark-Simulacrum. Use |
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
This comment has been minimized.
This comment has been minimized.
There is a PR already for this (rust-lang#124886), but looks like there are some issues with `f16`, `f128`, this commit just update it anyway for this custom branch
@rustbot author |
☔ The latest upstream changes (presumably #124213) made this pull request unmergeable. Please resolve the merge conflicts. |
d889fa8
to
2535624
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
Ah, I see what's happening - it looks like newest compiler-builtins provides intrinsics for f16 and f128, which are not supported by rustc yet: rust/compiler/rustc_symbol_mangling/src/v0.rs Line 322 in dde8cfa
compiler-builtins provides a dedicated feature-switch to disable those intrinsics: ... so, I guess, the question is: should rustc simply force-activate it? (if so, how? -- I'm not sure on this part) (funnily enough, |
Note that #125016 does the same thing, and has some more discussion about how to handle the f16/f128 feature |
Alright, I'm closing this one, since it's a duplicate of #125016 🙂 |
weak
attributes to all intrinsics compiler-builtins#598#[avr_skip]
for__addsf3
&__adddf3
compiler-builtins#601