rust/compiler/rustc_middle
bors ae7b1c1916 Auto merge of #127442 - saethlin:alloc-decoding-lock, r=oli-obk
Try to fix ICE from re-interning an AllocId with different allocation contents

As far as I can tell, based on my investigation in https://github.com/rust-lang/rust/issues/126741, the racy decoding scheme implemented here was never fully correct, but the arrangement of Allocations that's required to ICE the compiler requires some very specific MIR optimizations to create. As far as I can tell, GVN likes to create the problematic pattern, which is why we're noticing this problem now.

So the solution here is to not do racy decoding. If two threads race to decoding an AllocId, one of them is going to sit on a lock until the other is done.
2024-07-22 05:56:05 +00:00
..
src Auto merge of #127442 - saethlin:alloc-decoding-lock, r=oli-obk 2024-07-22 05:56:05 +00:00
Cargo.toml Use dep: for crate dependencies 2024-07-15 12:40:10 -04:00
messages.ftl Re-implement a type-size based limit 2024-07-02 15:48:48 -04:00
README.md

For more information about how rustc works, see the rustc dev guide.