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

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

1. Predator has provided 35 possible suspects.
2. Unable to find the suspect CL which caused this issue, hence adding CF-NeedsTriage label

Opened https://github.com/KhronosGroup/SPIRV-Tools/pull/1830 to fix this issue.  The problem is that spirv-opt think that a member of a struct cannot have type void, but it seems to be legal.  I changed spirv-opt to accept this.

It is invalid.  I've opened https://github.com/KhronosGroup/SPIRV-Tools/issues/1831 against the validator.

ClusterFuzz has detected this issue as fixed in range 583087:583101.

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

Fuzzer: libFuzzer_spvtools_opt_legalization_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  !t->AsVoid()
  spvtools::opt::analysis::Struct::Struct
  spvtools::opt::analysis::TypeManager::RecordIfTypeDefinition
  
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=583087:583101

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

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 6264343394779136 is verified as fixed, so closing issue as verified.

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