Reviewed-by: Jordan Justen
On Sat, Apr 6, 2013 at 7:45 PM, Paul Berry wrote:
> Commit 0fac0a6 (Modify tests for error checking on "flat" keyword to
> match updated specs) adopted the GLSL 1.50 rules for "flat" varyings
> for all desktop GL tests (the rationale was that this change likely
> refle
---
tests/all.tests | 3 +
tests/spec/gl-3.1/CMakeLists.gl.txt | 1 +
tests/spec/gl-3.1/primitive-restart-xfb.c | 259 ++
3 files changed, 263 insertions(+)
create mode 100644 tests/spec/gl-3.1/primitive-restart-xfb.c
diff --git a/t
Commit 0fac0a6 (Modify tests for error checking on "flat" keyword to
match updated specs) adopted the GLSL 1.50 rules for "flat" varyings
for all desktop GL tests (the rationale was that this change likely
reflects a bug fix rather than a deliberate behavioural difference).
The GLSL 1.50 rules all
From: Christoph Bumiller
v2: Removed dependency on TextureBarrierNV and ARB_tfb_2, added
comments.
---
.../spec/arb_texture_multisample/CMakeLists.gl.txt |1 +
.../spec/arb_texture_multisample/sample-position.c | 236
2 files changed, 237 insertions(+), 0 deletions(-)
From: Christoph Bumiller
Wrote this to figure out the sample positions on NVC0.
Didn't find any test that checks if the driver reported sample
positions match the behaviour of rendering.
It's probably a bit too crazy, but I thought I'd just send it in
case anyone wants to make use of it.
---
..
- Original Message -
> On 04/06/2013 03:21 AM, Jose Fonseca wrote:
> > Brian,
> >
> > Series looks alright, but it looks to me this is a pervasive issue, and not
> > just a few isolated cases:
> >
> > piglit $ git grep config.window_width | wc -l
> > 461
> >
> > So I wonder if there i
On 04/06/2013 03:21 AM, Jose Fonseca wrote:
Brian,
Series looks alright, but it looks to me this is a pervasive issue, and not
just a few isolated cases:
piglit $ git grep config.window_width | wc -l
461
So I wonder if there isn't a more definite solution. For example, could we
simply mo
Brian,
Series looks alright, but it looks to me this is a pervasive issue, and not
just a few isolated cases:
piglit $ git grep config.window_width | wc -l
461
So I wonder if there isn't a more definite solution. For example, could we
simply modify tests/util/... helper code to sanitize wind
- Original Message -
> Before, the 96x96 window got bumped up to 116x96 by Windows and we
> saw a "Got spurious window resize in automatic run" message and the
> test reported "warn".
> ---
> tests/texturing/lodbias.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> dif
