Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/8d29d92f4de952228af5a37b4603640b248bd576 ([wasm] Add I64Atomic Load/Store ops).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

The binaryen fuzzer enables atomic opcodes by default, which is behind a flag in Chrome. Updating this issue with the tracking bug for Atomics in V8. 

After triage, please leave a comment on if the bug can have security implications.

This bug hits unimplemented code on ARM, and is behind a flag (--experimental-wasm-threads), this issue should resolve itself once the implementation of I64Atomics on Arm32 is complete. 

ClusterFuzz has detected this issue as fixed in range 55026:55027.

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

Fuzzer: binaryen_wasm_fuzzer
Job Type: linux_asan_d8_v8_arm_dbg
Platform Id: linux

Crash Type: Ill
Crash Address: 0xf2dc209c
Crash State:
  v8::internal::compiler::InstructionSelector::VisitWord64AtomicLoad
  v8::internal::compiler::InstructionSelector::VisitNode
  v8::internal::compiler::InstructionSelector::VisitBlock
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=52252:52253
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_v8_arm_dbg&range=55026:55027

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

See https://github.com/google/clusterfuzz-tools for more information.

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