I started drafting tests for the new transform feedback mechanisms.
So far I have exercised the use of interleaved and separate modes
together (previously only one of the modes could be used at a time).
I first wrote a test using fixed set of varyings and two buffers.
Then I generalized it for
Signed-off-by: Topi Pohjolainen topi.pohjolai...@intel.com
---
tests/all.tests| 2 +
.../spec/arb_transform_feedback3/CMakeLists.gl.txt | 1 +
.../ext_interleaved_single_stream_many_buffers.c | 334 +
Make feedback buffer probe accessible also for other tests.
Original behavior is altered not to print matching values
anymore.
Signed-off-by: Topi Pohjolainen topi.pohjolai...@intel.com
---
tests/spec/ext_transform_feedback/separate.c | 30
Signed-off-by: Topi Pohjolainen topi.pohjolai...@intel.com
---
tests/all.tests| 3 +
tests/spec/CMakeLists.txt | 1 +
.../spec/arb_transform_feedback3/CMakeLists.gl.txt | 13 ++
tests/spec/arb_transform_feedback3/CMakeLists.txt |
This patch completely rewrites the threadpool module. This new
implementation is less complicated than the previous version. It also is
not an external project pulled in, but an original implementation.
This tries to be largely API compatible with the previous ThreadPool
implementation. And for
This patch removes the ConcurrentThreadPool singleton and opts instead
for creating two ThreadPools, one with multiple threads and a second one
that contains only one thread.
The reasoning for this change is two fold, first it gets rid of a rather
questionable use of a singleton, and second it
On 12 September 2013 10:47, Nicholas Mack nichm...@gmail.com wrote:
---
.../vs-gs-varyings-match-types.shader_test | 48
++
1 file changed, 48 insertions(+)
create mode 100644
tests/spec/glsl-1.50/execution/vs-gs-varyings-match-types.shader_test
This patch
On 12 September 2013 10:47, Nicholas Mack nichm...@gmail.com wrote:
---
.../gs-also-uses-smooth-flat-noperspective.geom| 25 ++
...also-uses-smooth-flat-noperspective.shader_test | 91
++
2 files changed, 116 insertions(+)
create mode 100644
---
.../compiler/layout-in-only-input-qualifier.geom | 23 +
.../compiler/layout-in-only-one-qualifier-id.geom | 24 ++
2 files changed, 47 insertions(+)
create mode 100644
tests/spec/glsl-1.50/compiler/layout-in-only-input-qualifier.geom
create mode
On 12 September 2013 10:47, Nicholas Mack nichm...@gmail.com wrote:
---
.../execution/vs-gs-arrays-fail.shader_test| 63
.../vs-gs-arrays-within-blocks-pass.shader_test| 86
++
2 files changed, 149 insertions(+)
create mode 100644
---
.../glsl-1.50/compiler/layout-max-verts-limited.geom| 17 +
1 file changed, 17 insertions(+)
create mode 100644 tests/spec/glsl-1.50/compiler/layout-max-verts-limited.geom
diff --git a/tests/spec/glsl-1.50/compiler/layout-max-verts-limited.geom
On Monday 16 September 2013 09:25:25 Eric Anholt wrote:
Dylan Baker baker.dyla...@gmail.com writes:
This series changes the way testlists are generated. This allows us to
generate a TestProfile object only once, at build time. This is
accomplished by using python's pickle module, which
On 16 September 2013 09:43, Paul Berry stereotype...@gmail.com wrote:
On 12 September 2013 10:47, Nicholas Mack nichm...@gmail.com wrote:
---
.../execution/vs-gs-arrays-fail.shader_test| 63
.../vs-gs-arrays-within-blocks-pass.shader_test| 86
---
...ayout-only-one-out-declaration-per-program.geom | 22 ++
.../compiler/layout-out-only-output-qualifier.geom | 22 ++
.../compiler/layout-out-order-irrelevant.geom | 21 +
3 files changed, 65 insertions(+)
create mode 100644
---
tests/all.tests| 12 ++
.../glsl-1.50/execution/geometry/CMakeLists.gl.txt | 2 +
.../geometry/gs-input-layout-qualifiers.c | 137
.../geometry/gs-output-layout-qualifiers.c | 139 +
4 files
---
tests/all.tests| 1 +
.../gl-3.2/layered-rendering/CMakeLists.gl.txt | 1 +
.../framebuffertexture-defaults.c | 180 +
3 files changed, 182 insertions(+)
create mode 100644
---
tests/all.tests| 1 +
.../gl-3.2/layered-rendering/CMakeLists.gl.txt | 1 +
.../layered-rendering/framebuffer-layer-complete.c | 197 +
3 files changed, 199 insertions(+)
create mode 100644
---
tests/all.tests| 1 +
.../gl-3.2/layered-rendering/CMakeLists.gl.txt | 1 +
.../framebuffer-layered-attachments.c | 166 +
3 files changed, 168 insertions(+)
create mode 100644
The Radeon driver writes GPU page faults to dmesg and we need to know which
test caused them.
If there is any change in dmesg during a test run, the test result is changed
as follows:
* pass - dmesg-warn
* warn - dmesg-warn
* fail - dmesg-fail
Dmesg is captured before and after the test and the
---
piglit-run.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/piglit-run.py b/piglit-run.py
index e8e11b7..7945b21 100755
--- a/piglit-run.py
+++ b/piglit-run.py
@@ -62,7 +62,7 @@ def main():
action = append,
metavar =
---
tests/quick-driver.tests | 14 --
tests/quick.tests| 6 ++
2 files changed, 6 insertions(+), 14 deletions(-)
delete mode 100644 tests/quick-driver.tests
diff --git a/tests/quick-driver.tests b/tests/quick-driver.tests
deleted file mode 100644
index f7c1a0f..000
(CC'ing Mesa-dev since this is a Mesa bug).
On 16 September 2013 11:00, Chad Versace chad.vers...@linux.intel.comwrote:
CC'ing Piglit.
On 09/14/2013 08:54 AM, Paul Berry wrote:
I'm investigating a failure in spec/OES_fixed_point/**attribute-arrays,
specifically the command line
Dylan Baker baker.dyla...@gmail.com writes:
This series changes the way testlists are generated. This allows us to
generate a TestProfile object only once, at build time. This is
accomplished by using python's pickle module, which stores a python
object representation as a plain text file.
Stupid question, but I'm stuck in an airport and can't research the answer
easily right now... Will this throw ?false? positives as a result of DPM
performance level changes on kernel 3.11+ (assuming dpm is enabled)? Is there
any way to filter these messages out besides disabling DPM?
On 13 September 2013 12:03, Brian Paul bri...@vmware.com wrote:
We obviously should require this extension.
---
tests/spec/ext_texture_array/compressed.c |1 +
1 file changed, 1 insertion(+)
diff --git a/tests/spec/ext_texture_array/compressed.c
On Mon, Sep 16, 2013 at 4:40 PM, Aaron Watry awa...@gmail.com wrote:
Stupid question, but I'm stuck in an airport and can't research the answer
easily right now... Will this throw ?false? positives as a result of DPM
performance level changes on kernel 3.11+ (assuming dpm is enabled)? Is
sampler types supported for textureLod and textureLodOffset:
sampler1D
sampler2D
sampler3D
sampler1DArray
sampler2DArray
isampler1D
isampler2D
isampler3D
isampler1DArray
isampler2DArray
usampler1D
usampler2D
usampler3D
usampler1DArray
usampler2DArray
---
tests/all.tests | 12
From: Kenneth Graunke kenn...@whitecape.org
From GLSL Spec 1.50 Section 8.7 (Texture Lookup Functions):
Texture lookup functions are available to vertex, geometry, and fragment
shaders.
Test sampler types avaiable for texture lookup functions in vertex, geometry,
and fragment shading
We could filter the messages with another command-line option taking a
regexp, but it's not a priority for me right now.
Marek
On Mon, Sep 16, 2013 at 10:40 PM, Aaron Watry awa...@gmail.com wrote:
Stupid question, but I'm stuck in an airport and can't research the answer
easily right now...
CC'ing Piglit.
On 09/14/2013 08:54 AM, Paul Berry wrote:
I'm investigating a failure in spec/OES_fixed_point/attribute-arrays,
specifically the command line
/home/pberry/.platform/piglit-mesa/piglit/build/bin/oes_fixed_point-attribute-arrays
-auto -fbo. It's segfaulting during piglit/waffle
That's good enough for me. Given that this is an optional piglit feature, it
shouldn't mess up what I'm working on anyway, and I definitely see the utility
of it for tracking down issues in a test run.
--Aaron
On Sep 16, 2013, at 6:00 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Mon,
31 matches
Mail list logo
