mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

interpret: always enable write_immediate sanity checks

Browse Source
This commit is contained in:
Ralf Jung 2024-09-29 08:30:46 +02:00
parent 1d9162bced
commit 7caf2cdc2c
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
compiler/rustc_const_eval/src/interpret/operand.rs
View File

@ -118,6 +118,7 @@ impl<Prov: Provenance> Immediate<Prov> {
(Immediate::Scalar(scalar), Abi::Scalar(s)) => { (Immediate::Scalar(scalar), Abi::Scalar(s)) => {
assert_eq!(scalar.size(), s.size(cx)); assert_eq!(scalar.size(), s.size(cx));
if !matches!(s.primitive(), abi::Pointer(..)) { if !matches!(s.primitive(), abi::Pointer(..)) {
// This is not a pointer, it should not carry provenance.
assert!(matches!(scalar, Scalar::Int(..))); assert!(matches!(scalar, Scalar::Int(..)));
} }
} }

6
compiler/rustc_const_eval/src/interpret/place.rs
View File

@ -652,6 +652,8 @@ where
M::after_local_write(self, local, /*storage_live*/ false)?; M::after_local_write(self, local, /*storage_live*/ false)?;
} }
// Double-check that the value we are storing and the local fit to each other. // Double-check that the value we are storing and the local fit to each other.
// Things can ge wrong in quite weird ways when this is violated.
// Unfortunately this is too expensive to do in release builds.
if cfg!(debug_assertions) { if cfg!(debug_assertions) {
src.assert_matches_abi(local_layout.abi, self); src.assert_matches_abi(local_layout.abi, self);
} }
@ -672,9 +674,9 @@ where
layout: TyAndLayout<'tcx>, layout: TyAndLayout<'tcx>,
dest: MemPlace<M::Provenance>, dest: MemPlace<M::Provenance>,
) -> InterpResult<'tcx> { ) -> InterpResult<'tcx> {
if cfg!(debug_assertions) { // We use the sizes from `value` below.
// Ensure that matches the type of the place it is written to.
value.assert_matches_abi(layout.abi, self); value.assert_matches_abi(layout.abi, self);
}
// Note that it is really important that the type here is the right one, and matches the // Note that it is really important that the type here is the right one, and matches the
// type things are read at. In case `value` is a `ScalarPair`, we don't do any magic here // type things are read at. In case `value` is a `ScalarPair`, we don't do any magic here
// to handle padding properly, which is only correct if we never look at this data with the // to handle padding properly, which is only correct if we never look at this data with the