tree 37d2ed11e4d064a628e715b4bb14b5ccee704e85
parent c75a1a46f39f93ecbd4bf86a0cb0ff84b387b6ba
author Alastair Donaldson <afdx@google.com> 1638602301 +0000
committer GitHub <noreply@github.com> 1638602301 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhqxY9CRBK7hj4Ov3rIwAALjQIAABMXVQLi/zMZ9zLAeZEe5yk
 mLhJKJhf8Tc8REkg3FhSnNtlVyqVjQFUzOKzaR9Q5E0tpdtXt2yUBCVvNGfu0FWv
 wecoqiut3E30Nd3BAIUJkuvivhCM0100Bu5jyjvwbfBbb7wLCmsQUeWCEWD0hO9Z
 3Z9cafETEq9L33JLlMa3e0vi52vm51x0qEMs5o9uI+casdHKe+Szj23IircnD9Ta
 yindFoIzlset1ZUE6363t2QwvdhfV6eyWPsD8JaDgGWsOAZ8B+f8FvowZhOdm5XS
 OE6wGsag9uqbu44dFv1vWFF1qztgpcDWe+FAr2j1BhAgqpHh18duk9M+TipIXxY=
 =ynIl
 -----END PGP SIGNATURE-----
 

Exit when ID overflow occurs in a fuzzing build (#4652)

Currently if an ID overflow occurs, spirv-opt (and other users of
IRContext) emits a warning and starts returning 0 when fresh ids are
requested. This tends to lead to crashes - such as null pointer
exceptions. When these arise during fuzzing they lead to auto-reported
bugs.

This change uses an ifdef guard to instead gracefully exit as soon as an
ID overflow occurs when the build is a fuzzing build.

Related issue: #4539.