about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2025-02-06 13:09:58 +0100
committerGitHub <noreply@github.com>2025-02-06 13:09:58 +0100
commit62cad970e86b00bd731226426cb259148679fbb7 (patch)
tree8ad2ef69a923d8599060c09282ee96f54f924dcd /compiler/rustc_codegen_gcc
parent7ca29360a7983323c0c3a9623ba8eef0cc68e663 (diff)
parentab3115990d333b8b782f8ea062c881fda377a353 (diff)
downloadrust-62cad970e86b00bd731226426cb259148679fbb7.tar.gz
rust-62cad970e86b00bd731226426cb259148679fbb7.zip
Rollup merge of #136235 - oli-obk:transmuty-pat-tys, r=RalfJung
Pretty print pattern type values with transmute if they don't satisfy their pattern

Instead of printing `0_u32 is 1..`, we now print the default fallback rendering that we also use for invalid bools, chars, ...: `{transmute(0x00000000): (u32) is 1..=}`.

These cases can occur in mir dumps when const prop propagates a constant across a safety check that would prevent the actually UB value from existing. That's fine though, as it's dead code and we always need to allow UB in dead code.

follow-up to https://github.com/rust-lang/rust/pull/136176

cc ``@compiler-errors`` ``@scottmcm``

r? ``@RalfJung`` because of the interpreter changes
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions