Some offenders are
- ValidateProtectedImage
- ValidateProtectedBuffer
- ValidateMemoryIsBoundToBuffer
- ValidateBufferUsageFlags
- ValidateDeviceAddressRange
I would rather use something like we do in cc_vuid_maps.cpp as it doesn't incur a constant string creation/copy each time these functions are call, assuming we don't need the VUs
These all have the issue around the fact they deal with copies which we sometimes have a different VU for the src and dst meaning we will need something where we make sure the Location has the vvl::Field to know which VUID to return
Some offenders are
I would rather use something like we do in
cc_vuid_maps.cppas it doesn't incur a constant string creation/copy each time these functions are call, assuming we don't need the VUsThese all have the issue around the fact they deal with copies which we sometimes have a different VU for the
srcanddstmeaning we will need something where we make sure theLocationhas thevvl::Fieldto know which VUID to return