diff options
| author | León Orell Valerian Liehr <me@fmease.dev> | 2025-05-18 11:03:46 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-18 11:03:46 +0200 |
| commit | e323c64fa4431de7d3cf4aceaf8a03f0c29897ac (patch) | |
| tree | c55fe139e79e3cec35e1646e1b20a825b744b836 /compiler/rustc_mir_transform/src | |
| parent | eb21b252c68411f2a0893d01292cf5d942800107 (diff) | |
| parent | 6128fca0b0b70ac6497bf5da38a5d3db37219f78 (diff) | |
| download | rust-e323c64fa4431de7d3cf4aceaf8a03f0c29897ac.tar.gz rust-e323c64fa4431de7d3cf4aceaf8a03f0c29897ac.zip | |
Rollup merge of #141045 - dpaoliello:noarmhazard, r=jieyouxu
[win][arm64] Remove 'Arm64 Hazard' undocumented MSVC option and instead disable problematic test PR #140758 added the undocumented `/arm64hazardfree` MSVC linker flag to work around a test failure where LLVM generated code that would trip a hazard in an outdated ARM processor. Adding this flag caused issues with LLD, as it doesn't recognize it. Rethinking the issue, using the undocumented flag seems like the incorrect solution: there's no guarantee that the flag won't be removed in the future, or change its meaning. Instead, I've disabled the problematic test for Arm64 Windows and have filed a bug with the MSVC team to have the check removed: <https://developercommunity.microsoft.com/t/Remove-checking-for-and-fixing-Cortex-A/10905134> This PR supersedes #140977 r? ```@jieyouxu```
Diffstat (limited to 'compiler/rustc_mir_transform/src')
0 files changed, 0 insertions, 0 deletions