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/+/c7ad5652d32a947355c58ed52a70049dd5d2bf01 ([Liftoff] Fix register reuse in merge init).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

ClusterFuzz has detected this issue as fixed in range 514517:514547.

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

Fuzzer: libFuzzer_v8_wasm_compile_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  CacheState::kMaxRegisterCode > reg.code() in liftoff-assembler.h
  v8::internal::wasm::LiftoffAssembler::GetNumUses
  v8::internal::wasm::LiftoffAssembler::GetBinaryOpTargetRegister
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514360:514382
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=514517:514547

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

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

Fixed already in https://chromium-review.googlesource.com/c/v8/v8/+/756705.
Was no security issue though.

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

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