-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
std: Update compiler-rt for more ABI fixes #37691
Conversation
This update of compiler-rt includes rust-lang/compiler-rt#26 which provides a targeted fix to the powisf2 intrinsics to keep rust-lang#37559 fixed but also address the new issue of rust-lang#37630. I've also [written up my thoughts][1] on why it appears that this is the correct fix for now (hoepfully at least). Closes rust-lang#37630 [1]: rust-lang/compiler-rt#26 (comment)
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
Nominating for beta as this is a stable-to-stable regression |
@bors r+ p=1 |
📌 Commit 2743128 has been approved by |
std: Update compiler-rt for more ABI fixes This update of compiler-rt includes rust-lang/compiler-rt#26 which provides a targeted fix to the powisf2 intrinsics to keep #37559 fixed but also address the new issue of #37630. I've also [written up my thoughts][1] on why it appears that this is the correct fix for now (hoepfully at least). Closes #37630 [1]: rust-lang/compiler-rt#26 (comment)
@alexcrichton Has this landed on beta yet? I don't see it in the commit log. |
@rillian AFAIK no |
@alexcrichton Ok, thanks for checking. Does the beta-accepted tag mean bors will land it, or should I submit a PR? We want this so we can update the gecko builders. |
Ah this doesn't happen automatically, we do so periodically from time to time. I've done so here: #37815 |
Thanks Alex! |
This update of compiler-rt includes rust-lang/compiler-rt#26 which provides a
targeted fix to the powisf2 intrinsics to keep #37559 fixed but also address
the new issue of #37630. I've also written up my thoughts on why it appears
that this is the correct fix for now (hoepfully at least).
Closes #37630