[Piglit] [PATCH 00/40] Replace vpfp-generic with shader_runner.
kenneth at whitecape.org
Sun Jun 7 22:31:00 PDT 2015
On Monday, June 08, 2015 06:29:26 AM Dave Airlie wrote:
> On 7 June 2015 at 12:11, Kenneth Graunke <kenneth at whitecape.org> wrote:
> > Hi all,
> > This patch series ports all vpfp-generic tests to shader_runner,
> > and then deletes vpfp-generic.
> > A bit of history:
> > - vpfp-generic was introduced by Nicolai Hähnle in 2009, as a generic
> > ARB_vertex|fragment_program test runner.
> > - shader_runner was introduced by Ian Romanick in 2010, as a generic
> > GLSL shader runner.
> > - shader_runner gained ARB program support in 2011 (courtesy of Eric Anholt).
> > At this point, vpfp-generic is fairly redundant - shader_runner can do
> > everything we need, and is much more widespread (12000+ tests). I've
> > been meaning to delete it for a few years, but never got around to it.
> > One difference is that the new tests don't glClear() before drawing. Since
> > they draw the entire window, it's pretty unnecessary, and just makes the
> > tests harder to debug. Many shader_runner tests don't bother clearing.
> This is actually annoying feature, esp if all tests use the same color
> for success,
> because we render one test, it passes, we render another test, it
> doesn't draw anything
> but it has gotten the back buffer from the previous tests, and it
> magically passes.
> This happens a lot more often on GPUs with VRAM.
I don't know...the tests probe the entire window...so the only failure
mode that will bite you like that is "the driver didn't render anything
at all." And the assumption is that, even with such a broken driver,
clearing will actually succeed at drawing...
Is that really so common? i965 will usually either draw something,
or fail so spectacularly that even clear doesn't work...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part.
More information about the Piglit