There is a hardware bug in i965/gen9+ with provoking vertices.
Test if workaround works correctly.
Ref: https://bugs.freedesktop.org/show_bug.cgi?id=103047
v2: - Vertices now have distinctive color
- Update message to reflect a nature of the bug which was
clarified by Kenneth. He will
Does this test do anything that isn't already done by the existing
clipflat.c test?
-Brian
On 06/14/2018 03:41 AM, Danylo Piliaiev wrote:
There is a hardware bug in i965/gen9+ with provoking vertices.
Test if workaround works correctly.
Ref:
https://na01.safelinks.protection.outlook.com/?url
This test covers situation mentioned in this bug
https://bugs.freedesktop.org/show_bug.cgi?id=106481 . Test is passing on
radeon and failing on intel i965.
On Wed, Jun 6, 2018 at 12:57 PM Illia Iorin wrote:
> This test checks that if we allocate more memory for the buffer
> than possible, we ge
I took a second look at 'clipflat' test and it doesn't test edge case in
question. 'clipflat' test doesn't fail on i965/gen9 while my test fails
(and passes on Radeon/sw), the difference is the necessity for my test
to have at least three vertices out of screen which have distinct color
from ve
Modified the unsized_array_member.shader_test to expect successful
linking instead of linker error.
According to the GLSLang Specification (version 4.60 Section 4.2 Scoping):
"An array implicitly sized in one shader can be explicitly sized by
another shader in the same stage. If no shader in a st
Modified the unsized_array_member.shader_test to expect successful
linking instead of linker error.
According to the GLSLang Specification (version 4.60 Section 4.2 Scoping):
"An array implicitly sized in one shader can be explicitly sized by
another shader in the same stage. If no shader in a st
Signed-off-by: Tapani Pälli
---
.../spec/arb_get_program_binary/CMakeLists.gl.txt | 1 +
tests/spec/arb_get_program_binary/xfb-varyings.c | 126 +
2 files changed, 127 insertions(+)
create mode 100644 tests/spec/arb_get_program_binary/xfb-varyings.c
diff --git a/tests/s
