diff options
| author | bors <bors@rust-lang.org> | 2025-05-17 07:00:46 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-05-17 07:00:46 +0000 |
| commit | b0e925903a04fc3b2e0903ce6110938e871c61a1 (patch) | |
| tree | 30d95198456eda853561328ed5b179b1577ecc61 /src/librustdoc/html/format.rs | |
| parent | a69bc17fb8026bdc0d24bb1896ff95f0eba1da4e (diff) | |
| parent | 734a5b1aa7888db3d86faffea1a15254022d68c9 (diff) | |
| download | rust-b0e925903a04fc3b2e0903ce6110938e871c61a1.tar.gz rust-b0e925903a04fc3b2e0903ce6110938e871c61a1.zip | |
Auto merge of #141024 - jieyouxu:revert-arm64ec, r=wesleywiser
Revert "Fix linking statics on Arm64EC #140176" This reverts PR #140176. Unfortunately, this will reopen https://github.com/rust-lang/rust/issues/138541 (re-breaking the `arm64ec-pc-windows-msvc` target). Unfortunately, multiple people are [reporting linker warnings related to `__rust_no_alloc_shim_is_unstable`](https://github.com/rust-lang/rust/pull/140176#issuecomment-2879715554) after this change in `x86_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 now[^timing], 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](https://github.com/rust-lang/rust/pull/140176#issuecomment-2881867433), we may have to cut a new beta and then repoint stage0 against that newer beta? cc `@dpaoliello` `@wesleywiser` r? `@wesleywiser` (or compiler) [^timing]: Note that it's still RustWeek this week, so most team members are N/A.
Diffstat (limited to 'src/librustdoc/html/format.rs')
0 files changed, 0 insertions, 0 deletions