tree 1989526172d7fd2f2a06658ce75b9b53f5f65b5c
parent 2fdea57d19d46d565f5517140f60ca87e72f5c8c
author Alastair Donaldson <afdx@google.com> 1585839286 +0100
committer GitHub <noreply@github.com> 1585839286 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJehfy2CRBK7hj4Ov3rIwAAdHIIABKePbEP9RM3X++ou9Mb47fB
 mHQh4suFlNJurxTAWxtCt5gjDkh49NbTa1EPR0y1WvtgX5tiWRWLEhUYrawDpnXL
 ut4h/n/VRjWAFG8q2kGhqfEPFfrFcuXg9GrOyjL9QDhq+mv+AxSdeOk6NUPqSext
 7WSn84gZ7+RhHf8TNZkQfz6BH0k0L05ZnZCJEewSeBfjG0ilfV9FmqJTSwu056YT
 dtdYZa3br1MKgdk8egCbkRuhyNjgaER4QngYnMw8/SeqRKp0XwkE/dPIe0qXK6Kk
 6T5YDLq/E9FyYSMwPGciV2+iSInlhtS0/MwGEVEW5n/CvHvb0M4QKLZqDUc7Et0=
 =WDQm
 -----END PGP SIGNATURE-----
 

spirv-fuzz: Introduce TransformationContext (#3272)

Some transformations (e.g. TransformationAddFunction) rely on running
the validator to decide whether the transformation is applicable.  A
recent change allowed spirv-fuzz to take validator options, to cater
for the case where a module should be considered valid under
particular conditions.  However, validation during the checking of
transformations had no access to these validator options.

This change introduced TransformationContext, which currently consists
of a fact manager and a set of validator options, but could in the
future have other fields corresponding to other objects that it is
useful to have access to when applying transformations.  Now, instead
of checking and applying transformations in the context of a
FactManager, a TransformationContext is used.  This gives access to
the fact manager as before, and also access to the validator options
when they are needed.