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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Automatically adding ccs based on suspected regression changelists:

Update OpPhi instructions after splitting block. (#1783) by 31666470+s-perron@users.noreply.github.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/ce644d4a2484fe66e53f5b744ebc4d0d5d49e1ca

Remove using std::<foo> statements. (#1756) by dj2@everburning.com - https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+/a5a5ea0e2dfce9c755a88af1074ebe68a44d2ed9

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Predator and CL could not provide any possible suspects.
For the recent changes made to the file, “fold.cpp” assigning to stevenperron@.

@stevenperron -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.

https://github.com/KhronosGroup/SPIRV-Tools/pull/2292

ClusterFuzz has detected this issue as fixed in range 623459:623461.

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

Fuzzer: libFuzzer_spvtools_opt_size_fuzzer
Fuzz target binary: spvtools_opt_size_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  spvtools::opt::InstructionFolder::BinaryOperate
  spvtools::opt::InstructionFolder::FoldScalars
  spvtools::opt::InstructionFolder::FoldInstructionToConstant
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=580304:580310
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=623459:623461

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

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

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