diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-06-26 15:47:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-26 15:47:19 +0200 |
| commit | d73bf103b9040a417ab5dacc3e93cb487b49f397 (patch) | |
| tree | 6c9a4dc6b8c7cc1580e097ed6f3c3e50fe15a4d0 /compiler/rustc_resolve/src | |
| parent | cbcf183711f637054e18f272ecfbf8d2ae8588c0 (diff) | |
| parent | 233882128bda3d1912d339afeca985637f94485c (diff) | |
| download | rust-d73bf103b9040a417ab5dacc3e93cb487b49f397.tar.gz rust-d73bf103b9040a417ab5dacc3e93cb487b49f397.zip | |
Rollup merge of #142285 - workingjubilee:dont-use-bad-assembly, r=nnethercote
tests: Do not run afoul of asm.validity.non-exhaustive in input-stats This addresses one of the three powerpc64-unknown-linux-musl test failures in https://github.com/rust-lang/rust/issues/142280 I was motivated to cover it myself because technically this is also compile-time UB if we compile a program that has `asm!` with x86-64-specific instructions on another platform. That'll only mean something if this is ever switched to build-pass, or if checking emits object code, but conveniently "nop" is valid assembly on all platforms anyone has implemented Rust codegen for. Even the weird ones LLVM doesn't support, like PA-RISC or Common Intermediate Language. ...except GPUs. Not sure about those. r? ```@nnethercote```
Diffstat (limited to 'compiler/rustc_resolve/src')
0 files changed, 0 insertions, 0 deletions