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

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

Fix with https://github.com/KhronosGroup/SPIRV-Tools/pull/1799.

ClusterFuzz has detected this issue as fixed in range 581969:581979.

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  (IsLoad() || opcode() == SpvOpStore || opcode() == SpvOpAccessChain || opcode() 
  spvtools::opt::Instruction::GetBaseAddress
  spvtools::opt::MemPass::GetPtr
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=579911:580305
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=581969:581979

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

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.

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

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