about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorJacob Pratt <jacob@jhpratt.dev>2024-04-03 20:17:06 -0400
committerGitHub <noreply@github.com>2024-04-03 20:17:06 -0400
commit4332498a6daff23e4403d9bce43d97ed63cad382 (patch)
tree63b208519d39cbf79b2a46a4398a19d2de7ae7c4 /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parent819568a7b41cf5b453df675b41569b311216460c (diff)
parent2d47cd77ac7b41a08f5c2ebc22035ed2f39dc076 (diff)
downloadrust-4332498a6daff23e4403d9bce43d97ed63cad382.tar.gz
rust-4332498a6daff23e4403d9bce43d97ed63cad382.zip
Rollup merge of #123401 - Zalathar:assert-size-aarch64, r=fmease
Check `x86_64` size assertions on `aarch64`, too

(Context: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Checking.20size.20assertions.20on.20aarch64.3F)

Currently the compiler has around 30 sets of `static_assert_size!` for various size-critical data structures (e.g. various IR nodes), guarded by `#[cfg(all(target_arch = "x86_64", target_pointer_width = "64"))]`.

(Presumably this cfg avoids having to maintain separate size values for 32-bit targets and unusual 64-bit targets. Apparently it may have been necessary before the i128/u128 alignment changes, too.)

This is slightly incovenient for people on aarch64 workstations (e.g. Macs), because the assertions normally aren't checked until we push to a PR. So this PR adds `aarch64` to the `#[cfg(..)]` guarding all of those assertions in the compiler.

---

Implemented with a simple find/replace. Verified by manually inspecting each `static_assert_size!` in `compiler/`, and checking that either the replacement succeeded, or adding aarch64 wouldn't have been appropriate.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions