2-post thread. The real 'buffer zoo' problem with Vulkan: need HW
instruction emulation macros with overcomplete both {offset, index}
inputs so emulation can choose the right path based on whatever
{SSBO, TEXEL_BUFFER, future pointer}. TEXEL_BUFFER for formats one
can't load from SSBOs, both need 'indexes', and whenever IHVs actually
correctly optimize the pointer extension, one needs byte offsets.
'Deadcode removal nightmare land wins today.' Sibling to the
1870351985855119449 STORAGE_TEXEL_BUFFER aliasing thread.
ed
2f60019cbd