diff options
| author | bors <bors@rust-lang.org> | 2023-03-31 08:50:35 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-03-31 08:50:35 +0000 |
| commit | 22a7a19f9333bc1fcba97ce444a3515cb5fb33e6 (patch) | |
| tree | 8ac7da60c0ee60d36ef565024a75f848c98a19b6 /compiler/rustc_codegen_ssa/src/errors.rs | |
| parent | ec7bb8da11f3e5cc73be397b78d2aea4157df300 (diff) | |
| parent | 750707801b42c0da6beeccd587925130ba2bad99 (diff) | |
| download | rust-22a7a19f9333bc1fcba97ce444a3515cb5fb33e6.tar.gz rust-22a7a19f9333bc1fcba97ce444a3515cb5fb33e6.zip | |
Auto merge of #98112 - saethlin:mir-alignment-checks, r=oli-obk
Insert alignment checks for pointer dereferences when debug assertions are enabled Closes https://github.com/rust-lang/rust/issues/54915 - [x] Jake tells me this sounds like a place to use `MirPatch`, but I can't figure out how to insert a new basic block with a new terminator in the middle of an existing basic block, using `MirPatch`. (if nobody else backs up this point I'm checking this as "not actually a good idea" because the code looks pretty clean to me after rearranging it a bit) - [x] Using `CastKind::PointerExposeAddress` is definitely wrong, we don't want to expose. Calling a function to get the pointer address seems quite excessive. ~I'll see if I can add a new `CastKind`.~ `CastKind::Transmute` to the rescue! - [x] Implement a more helpful panic message like slice bounds checking. r? `@oli-obk`
Diffstat (limited to 'compiler/rustc_codegen_ssa/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
