Another --validate-asm issue. Reproduces on TOT.

Thanks! AFACIT, the new validator should not suffer from this problem. I'll keep the issue open until new validator is enabled.

ClusterFuzz has detected this issue as fixed in range 469332:469353.

Detailed report: https://clusterfuzz.com/testcase?key=5926602182754304

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x00000004
Crash State:
  v8::internal::wasm::AsmWasmBuilderImpl::LookupOrInsertFunction
  v8::internal::wasm::AsmWasmBuilderImpl::VisitCallExpression
  v8::internal::wasm::AsmWasmBuilderImpl::VisitForEffect
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=435209:435261
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=469332:469353

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5926602182754304


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5926602182754304 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Yep, has been fixed by switching to new asm.js validator.