HeapStoreOptimization: Fix a bug with jumping from the later value (v2) (#7070)

This PR fixes this situation:

(block $out
  (local.set $x (struct.new X Y Z))
  (struct.set $X 0 (local.get $x) (..br $out..))  ;; X' here has a br
)
(local.get $x)

=>

(block $out
  (local.set $x (struct.new (..br $out..) Y Z))
)
(local.get $x)

We want to fold the struct.set into the struct.new, but the br is
a problem: if it executes then we skip the struct.set, and the last
local.get in fact reads the struct before the write. And, if we did this
optimization, we'd end up with the br on the struct.new, so it
would skip that instruction and even the local.set.

To fix this, we use the new API from #7039, which lets us query,
"is it ok to move the local.set to where the struct.set is?"

0 files changed, 0 insertions, 0 deletions