git.lizzy.rs Git - rust.git/commit - compiler/rustc_codegen

author	bors <bors@rust-lang.org>
	Wed, 21 Dec 2022 23:20:04 +0000 (23:20 +0000)
committer	bors <bors@rust-lang.org>
	Wed, 21 Dec 2022 23:20:04 +0000 (23:20 +0000)
commit	bdbe392a13bc9782b98de193c3751b9d96bb5fcc
tree	860c50e7741ae8896129546d16d0a65956364b33	tree \| snapshot
parent	b569c9dc57ee22b6ff94563af856909763dfa24b	commit \| diff
parent	6f21ba4a06b7fa17113b7029c4aa7805db16aa32	commit \| diff

Auto merge of #105613 - Nilstrieb:rename-assert_uninit_valid, r=RalfJung

Rename `assert_uninit_valid` intrinsic

It's not about "uninit" anymore but about "filling with 0x01 bytes" so the name should at least try to reflect that.

This is actually not fully correct though, as it does still panic for all uninit with `-Zstrict-init-checks`. I'm not sure what the best way is to deal with that not causing confusion. I guess we could just remove the flag? I don't think having it makes a lot of sense anymore with the direction that we have chose to go. It could be relevant again if #100423 lands so removing it may be a bit over eager.

r? `@RalfJung`

compiler/rustc_codegen_cranelift/src/intrinsics/mod.rs	diff1 \|	diff2 \|	blob \| history
compiler/rustc_codegen_ssa/src/mir/block.rs	diff1 \|	diff2 \|	blob \| history
compiler/rustc_const_eval/src/interpret/intrinsics.rs	diff1 \|	diff2 \|	blob \| history
compiler/rustc_span/src/symbol.rs	diff1 \|	diff2 \|	blob \| history