On Sat, Nov 24, 2018 at 9:17 AM apinheiro wrote:
> Then do you think that your test is still needed? An alternative, as we
> didn't add any compute shader using ubo/ssbo, would be rename and update
> the description of your test (something like "compute shader using ubo").
No, my test shouldn't
On 23/11/18 19:41, Józef Kucia wrote:
> On Thu, Nov 22, 2018 at 11:21 AM apinheiro wrote:
>> some weeks ago I sent a series with ubo/ssbo tests (still pending review)
>>
>> https://lists.freedesktop.org/archives/piglit/2018-September/025116.html
>>
>> All those has the name stripped. Could you
On Thu, Nov 22, 2018 at 11:21 AM apinheiro wrote:
> some weeks ago I sent a series with ubo/ssbo tests (still pending review)
>
> https://lists.freedesktop.org/archives/piglit/2018-September/025116.html
>
> All those has the name stripped. Could you try them and see if any of
> them triggers the
Hi,
some weeks ago I sent a series with ubo/ssbo tests (still pending review)
https://lists.freedesktop.org/archives/piglit/2018-September/025116.html
All those has the name stripped. Could you try them and see if any of
them triggers the NVIDIA bug you found?
BR
On 21/11/18 16:23, Józef
This test reproduces a bug in Nvidia drivers:
error: binding mismatch between shaders for UBO (named __defaultname)
error: struct type mismatch between shaders for uniform (named __defaultname)
error: binding mismatch between shaders for UBO (named __defaultname)
error: struct type mismatch
