2 Commits

Author	SHA1	Message	Date
Jeff Bolz	38cbad15ca	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.	2019-03-05 14:40:07 -06:00
Jeff Bolz	9f2aec49e9	GL_EXT_buffer_reference	2019-01-07 12:36:13 -06:00