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/+/e5847dd82ae591bd3ba2d3d3dd42a9a73158a548 ([fuzzer] Improve wasm-compile fuzzer).

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 following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/8518d12200377dd3308dbe5b043618d5cca0c665

commit 8518d12200377dd3308dbe5b043618d5cca0c665
Author: Clemens Hammacher <clemensh@chromium.org>
Date: Fri Jan 11 10:57:09 2019

[Liftoff] Fix sub of the same register

In the degenerate case where we wanted to emit {x = x - x} (where {x}
is any register), ia32 and x64 generated wrong code (producing {-x + -x}
instead). Fix this by special casing this case.

R=ahaas@chromium.org

Bug:  chromium:919308 
Change-Id: I9cd9818d2a678450ac6530107e7a5cbb625ddb8d
Reviewed-on: https://chromium-review.googlesource.com/c/1405029
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#58731}
[modify] https://crrev.com/8518d12200377dd3308dbe5b043618d5cca0c665/src/wasm/baseline/ia32/liftoff-assembler-ia32.h
[modify] https://crrev.com/8518d12200377dd3308dbe5b043618d5cca0c665/src/wasm/baseline/x64/liftoff-assembler-x64.h
[add] https://crrev.com/8518d12200377dd3308dbe5b043618d5cca0c665/test/mjsunit/regress/wasm/regress-919308.js

ClusterFuzz has detected this issue as fixed in range 622033:622035.

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

Fuzzer: afl_v8_wasm_compile_fuzzer
Fuzz target binary: v8_wasm_compile_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Ill
Crash Address: 0x55dfb26e5aa8
Crash State:
  v8::internal::wasm::fuzzer::WasmExecutionFuzzer::FuzzWasmModule
  wasm-compile.cc
  ExecuteFilesOnyByOne
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=609145:609147
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=622033:622035

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

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

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

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