// PTAL different repros lead to different output. E.g.:
function __f_8() {
  "use asm";
  function __f_10(a,b,c) {
    a = a | 0;
    b = b | 0;
    c = c | 0;
    var __v_7 = 0;
    __v_7 = __v_9[a & 1073741823]() | 1073741823;
  }
}
__f_8();

// Output:
# Compared x64,ignition with x64,ignition_asm
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt
# Flags of x64,ignition_asm:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt --validate-asm --stress-validate-asm --suppress-asm-messages
#
# Difference:
+ terminate called after throwing an instance of 'std::length_error'
#
# Source file:
none
#
### Start of configuration x64,ignition:

### End of configuration x64,ignition
#
### Start of configuration x64,ignition_asm:
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_default_append
Received signal 6

==== C stack trace ===============================

 [0x7f5870a30914]
 [...]
[end of stack trace]

// And:
function __f_8() {
  "use asm";
  function __f_10(a,b,c) {
    a = a | 0;
    b = b | 0;
    c = c | 0;
    return __v_9[a & 1073741823]() | 1073741823;
  }
}
__f_8();

// Output:
# Compared x64,ignition with x64,ignition_asm
#
# Flags of x64,ignition:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt
# Flags of x64,ignition_asm:
--abort_on_stack_overflow --expose-gc --allow-natives-syntax --invoke-weak-callbacks --omit-quit --es-staging --random-seed 732681078 --ignition --turbo-filter=~ --hydrogen-filter=~ --noopt --validate-asm --stress-validate-asm --suppress-asm-messages
#
# Difference:
+ terminate called after throwing an instance of 'std::length_error'
#
# Source file:
none
#
### Start of configuration x64,ignition:

### End of configuration x64,ignition
#
### Start of configuration x64,ignition_asm:
terminate called after throwing an instance of 'std::length_error'
  what():  vector::_M_default_append
Received signal 6

==== C stack trace ===============================

 [0x7ff163a60914]
 [...]
[end of stack trace]

### End of configuration x64,ignition_asm

// Ignore comment 2. There's no other difference... was seeing it wrong.

Thanks! Will cook up a fix soon.

ClusterFuzz has detected this issue as fixed in range 45428:45429.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,ignition_asm
  sources: none
  
Sanitizer: address (ASAN)

Regressed: V8: 44685:44686
Fixed: V8: 45428:45429

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


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.