about summary refs log tree commit diff
path: root/compiler/rustc_interface/src/errors.rs
diff options
context:
space:
mode:
authorDylan DPC <99973273+Dylan-DPC@users.noreply.github.com>2022-08-29 16:49:40 +0530
committerGitHub <noreply@github.com>2022-08-29 16:49:40 +0530
commit3ea5456366170f2b39bd77070c00c632537ec591 (patch)
treeaba6fa2bbb0c58508a1d67cb5b7a85a36f665f15 /compiler/rustc_interface/src/errors.rs
parent5555e13a6ec5268612e85baa3af62ddf95fa2517 (diff)
parentaff9841507d2e0caef015c523fd8f41848b0c2f9 (diff)
downloadrust-3ea5456366170f2b39bd77070c00c632537ec591.tar.gz
rust-3ea5456366170f2b39bd77070c00c632537ec591.zip
Rollup merge of #100239 - RalfJung:const-prop-uninit, r=oli-obk
remove an ineffective check in const_prop

Based on https://github.com/rust-lang/rust/pull/100043, only the last two commits are new.

ConstProp has a special check when reading from a local that prevents reading uninit locals. However, if that local flows into `force_allocation`, then no check fires and evaluation proceeds. So this check is not really effective at preventing accesses to uninit locals.

With https://github.com/rust-lang/rust/pull/100043, `read_immediate` and friends always fail when reading uninit locals, so I don't see why ConstProp would need a separate check. Thus I propose we remove it. This is needed to be able to do https://github.com/rust-lang/rust/pull/100085.
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions