[test] Fix Handle dereference issue in move fuzzer (bis)

Another instance of:
https://chromium-review.googlesource.com/c/v8/v8/+/4066541

R=dmercadier@chromium.org
CC=machenbach@chromium.org

Bug: v8:13544
Change-Id: Id9046bf9c5ea09aff45b4531b5f1ad03307fd100
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4221571
Reviewed-by: Darius Mercadier <dmercadier@chromium.org>
Commit-Queue: Thibaud Michaud <thibaudm@chromium.org>
Cr-Commit-Position: refs/heads/main@{#85644}
This commit is contained in:
Thibaud Michaud 2023-02-03 13:03:28 +01:00 committed by V8 LUCI CQ
parent 1885a16551
commit df0e9dca39

View File

@ -838,7 +838,8 @@ class TestEnvironment : public HandleAndZoneScope {
for (auto move : *moves) {
int to_index = OperandToStatePosition(
TeardownLayout(), AllocatedOperand::cast(move->destination()));
state_out->set(to_index, GetMoveSource(state_in, move));
Object source = GetMoveSource(state_in, move);
state_out->set(to_index, source);
}
// If we generated redundant moves, they were eliminated automatically and
// don't appear in the parallel move. Simulate them now.