When storage textures are in the resource table, the implementation doesn't know a priori which resources have been accessed. In particular for writable resources (storage texture/buffers) it can't know if a memory barrier is necessary. Requiring implementations to always emit a barrier between usage scopes using the resource table, just in case, would be very pessimizing. Is there a better alternative?
When storage textures are in the resource table, the implementation doesn't know a priori which resources have been accessed. In particular for writable resources (storage texture/buffers) it can't know if a memory barrier is necessary. Requiring implementations to always emit a barrier between usage scopes using the resource table, just in case, would be very pessimizing. Is there a better alternative?