-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Revert "Fix linking statics on Arm64EC #140176" #141024
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
base: master
Are you sure you want to change the base?
Conversation
Unfortunately, multiple people are reporting linker warnings related to `__rust_no_alloc_shim_is_unstable` after this change. The solution isn't quite clear yet, let's revert to green for now, and try a reland with a determined solution for `__rust_no_alloc_shim_is_unstable`. This reverts commit c8b7f32, reversing changes made to 667247d.
Some changes occurred in compiler/rustc_codegen_ssa These commits modify compiler targets. |
Nominating this for beta backport because people are reporting seeing the linker warning in bootstrapping as well. However, the beta backport is a "pick your poison" situation, where we avoid the linker warnings in Tier 1 @rustbot label: +beta-nominated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me when CI is green
CI is green. |
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
This reverts PR #140176.
Unfortunately, this will reopen #138541 (re-breaking the
arm64ec-pc-windows-msvc
target).Unfortunately, multiple people are reporting linker warnings related to
__rust_no_alloc_shim_is_unstable
after this change inx86_64-pc-windows-msvc
as well. The solution isn't quite clear yet, let's revert to avoid the linker warnings on the Tier 1 MSVC target for now1, and try a reland with a determined solution for__rust_no_alloc_shim_is_unstable
.Judging from people reporting that they are observing this also when bootstrapping w/ stage0 rustc, we may have to cut a new beta and then repoint stage0 against that newer beta?
cc @dpaoliello @wesleywiser
r? @wesleywiser (or compiler)
Footnotes
Note that it's still RustWeek this week, so most team members are N/A. ↩