Properly set storage and memory after erasing potentially destroyed keys

This commit is contained in:
chriseth
2019-08-13 18:43:15 +02:00
parent abed8119fc
commit e396dc7246
3 changed files with 44 additions and 4 deletions
@@ -0,0 +1,21 @@
{
let a := 0
let b := 1
let c := 2
mstore(a, b)
sstore(0, mload(a))
mstore(a, c)
sstore(10, mload(a))
}
// ====
// step: loadResolver
// ----
// {
// let a := 0
// let b := 1
// let c := 2
// mstore(a, b)
// sstore(a, b)
// mstore(a, c)
// sstore(10, c)
// }
@@ -0,0 +1,21 @@
{
let a := 0
let b := 1
let c := 2
sstore(a, b)
mstore(0, sload(a))
sstore(a, c)
mstore(32, sload(a))
}
// ====
// step: loadResolver
// ----
// {
// let a := 0
// let b := 1
// let c := 2
// sstore(a, b)
// mstore(a, b)
// sstore(a, c)
// mstore(32, c)
// }