tree afc2227a72a095f7dbc7bfeb4b827958673a1c5e
parent 9390154c557e6211e273628805a1827a4738c751
author Jeff Bolz <jbolz@nvidia.com> 1551818407 -0600
committer Jeff Bolz <jbolz@nvidia.com> 1551818407 -0600

Fix interactions between 'volatile' and the Vulkan memory model

Last year we changed 'volatile' to also act as 'coherent', but when I
resolved the memory model changes against that change I missed handling
volatile in a couple places that we check for coherent. There was also
a place in post-processing that acted as if the volatile memory access
flag has a literal number associated with it, when it doesn't.