Created attachment 144613 [details]
Renderdoc trace of affected frame
I've encountered a curious situation using RADV regarding texel buffer access in vertex shaders. I have 3 buffers mapped to texel buffer inputs and I cannot properly access both at the same time. Curiously, if one buffer object is viewed in more than one buffer view, everything is ok. If I comment out all access to one of the loads in renderdoc the fetches seem to work fine as long as the other is not referenced in the shader. I have attached a renderdoc trace showing this behaviour. The renderdoc eventID of interest is no 97 which is supposed to render a cube.
This issue has been confirmed by at least one other RADV user with an RX570. Changing the driver to amdvlk makes the issue go away. Hopefully I merley overlooked something but khronos' validation layer gives no errors or warnings.
Application: RPCS3 emulator
Mesa version: Mesa 19.2.0-devel (git-21dd881 2019-06-20 bionic-oibaf-ppa)
RADV version: 'AMD RADV POLARIS10 (LLVM 8.0.0)' running on driver 19.1.99
This only seems to happen with LLVM 8. The capture replays fine for me with latest LLVM 9.0-git.
Confirmed. Switched to padoka drivers which are llvm9 and the issue is not present.