diff options
| author | bors <bors@rust-lang.org> | 2023-07-21 19:32:17 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-07-21 19:32:17 +0000 |
| commit | d908a5b08e9ccbd2b41f8b399aa6cd919d5cb451 (patch) | |
| tree | acb2921e0160ca30e1264981ecd0158be2a2b49f /compiler/rustc_codegen_llvm/src/context.rs | |
| parent | c3c5a5c5f7a0cf9acdfe60440a1e1fa68a1c1278 (diff) | |
| parent | 41a73d8251553afa39c7082b44b2781ca4898578 (diff) | |
| download | rust-d908a5b08e9ccbd2b41f8b399aa6cd919d5cb451.tar.gz rust-d908a5b08e9ccbd2b41f8b399aa6cd919d5cb451.zip | |
Auto merge of #113892 - RalfJung:uninit-undef-poison, r=wesleywiser
clarify MIR uninit vs LLVM undef/poison In [this LLVM discussion](https://discourse.llvm.org/t/rfc-load-instruction-uninitialized-memory-semantics/67481) I learned that mapping our uninitialized memory in MIR to poison in LLVM would be quite problematic due to the lack of a byte type. I am not sure where to write down this insight but this seems like a reasonable start.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions