search for: shader_test

Displaying 15 results from an estimated 15 matches for "shader_test".

2014 Jan 10
0
commit 0a1479c829 breaks glsl-fs-lots-of-tex.shader_test on nv50/nvc0
On Thu, Jan 9, 2014 at 4:04 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Hi Marek, > > I won't pretend to understand what's going on, but I just bisected a > failure on tests/shaders/glsl-fs-lots-of-tex.shader_test in piglit > between 9.1 and HEAD, and it landed on your commit. It's approximately > the simplest shader known to man (esp at HEAD when all the TEX > instructions are gone due to CSE), so I'm guessing there's some edge > condition in the copying logic triggered by it. Chris...
2015 May 25
4
[RFC PATCH 00/11] Implement ARB_cull_distance
...inition maybe. >> >> though it doesn't solve the does nvidia do the right thing with >> cull[0] and clip[0], and what is the right thing. >> >> Dave. > > > I'm still convinced that both clip[0] and cull[0] should be possible. Plus i > have written a shader_test for this a while ago which you pushed to piglit > (fs-cull-and-clip-distance-different.shader_test). If i remember right > nvidia passed that test just fine. My take (and note that I last read the extension many months ago) is that you're supposed to figure out the max gl_ClipDistance[]...
2015 May 25
2
[RFC PATCH 00/11] Implement ARB_cull_distance
On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: > It's the same on Radeon. There are 2x ClipOrCullDistance output > vectors and a mask saying it should clip or cull or do nothing. > > Marek > My thinking was gallium should have a single semantic and a mask in the shader definition maybe. though it doesn't solve the does nvidia do the right thing with
2014 Feb 14
0
Regression caused by 2e9ee44797 ("nv50/ir/ra: some register spilling fixes")
Hi Christoph, bin/shader_runner tests/spec/glsl-1.40/uniform_buffer/fs-struct-copy-complicated.shader_test -auto bin/shader_runner tests/spec/glsl-1.40/uniform_buffer/vs-struct-copy-complicated.shader_test -auto bin/shader_runner tests/spec/glsl-1.50/uniform_buffer/gs-struct-copy-complicated.shader_test -auto Now all segfault. I reverted 2e9ee44797 ("nv50/ir/ra: some register spilling fixes")...
2014 May 29
1
[PATCH 2/4] nvc0/ir: Handle reverse subop for OP_EXTBF when folding constant expressions
Tested with: MESA_EXTENSION_OVERRIDE=GL_ARB_gpu_shader5 ./shader_runner ../tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-bitfieldReverse.shader_test -> green output, so this should be ok the test was not change though... On 29.05.2014 21:47, Ilia Mirkin wrote: > Can you verify that you tested how the HW handles this, as well as > exactly how you did it (i.e. how did you modify the code + piglit > test, what the results were, etc...
2015 Nov 05
1
[PATCH envytools] envydis: gk110: Add support for dadd with an immediate src
This commit adds support for dadd with an immediate src in gk110 code. The machine-code in question is generated by e.g. nouveau_compiler with the new "Make use of double immediates" patch series when building the piglit glsl-algebraic-double-add.shader_test. This commit changes the output from: 00000010: 001c0001 c38001ff $r0 $r0 $r0 $r0 0x3fe00 0x3fe00 0x3fe0000000000000 0x3fe00000 0x0 0x3 ??? [unknown: 00000000 c0800000] [unknown instruction] Into: 00000010: 001c0001 c38001ff add rn f64 $r0d $r0d 0x3fe0000000000000 The machine-code...
2015 May 27
2
[RFC PATCH 00/11] Implement ARB_cull_distance
...doesn't solve the does nvidia do the right thing with >>>> cull[0] and clip[0], and what is the right thing. >>>> >>>> Dave. >>> >>> I'm still convinced that both clip[0] and cull[0] should be possible. Plus i >>> have written a shader_test for this a while ago which you pushed to piglit >>> (fs-cull-and-clip-distance-different.shader_test). If i remember right >>> nvidia passed that test just fine. Ah btw, if we follow Brian Paul, overlapping indexes are fine! (and it is way more intuitive to use for a shader deve...
2015 May 18
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...hat the actual shader code is correct... so I'm doing something funny wrong. (And yeah, tons of missed optimization opportunities in this code, but let's not dwell on that.) This is the piglit test: http://cgit.freedesktop.org/piglit/tree/tests/spec/arb_tessellation_shader/execution/quads.shader_test It should be noted that other piglit tests don't exhibit this error, however they also tend to be simpler. One key difference is that they don't change the patch size in TCS. I'm including a link to a text file with the tessellation control and evaluation shaders (decoded with nvdisasm...
2019 Jul 18
3
[Bug 111167] New: Dividing zero by a uniform in loop header causes segfault in nv50_ir::NVC0LegalizeSSA::handleDIV
...ponent: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: abelbriggs1 at hotmail.com QA Contact: nouveau at lists.freedesktop.org Created attachment 144815 --> https://bugs.freedesktop.org/attachment.cgi?id=144815&action=edit Reproduction shader_test file, core dump of crash The attached archive contains a shader that, on the build and PC specified below, causes a segmentation fault in nouveau when run. A core dump of the crash is supplied as well. void main() { for(int i = 1; 1 >= (0 / int((injectionSwitch.y))); 1) { } } The value...
2013 Jul 06
4
[Bug 66642] New: [nva5] Wrong provoking vertex is selected for flat attribute interpolation (clipping?)
...fied OS: Linux (All) Reporter: alzeih at gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/nouveau Product: Mesa The following piglit test: interpolation-flat-gl_BackColor-smooth-none.shader_test appears to select the wrong provoking vertex depending on the exact value of v[0].y. For v[0].y > -1.0, the triangle ends up red. For v[0].y = -1.0, the triangle ends up green. For v[0].y < -1.0, the triangle ends up (correctly) blue. Hardware: nva5 (GT330M) in MacBookPro6,2 Mesa version:...
2015 May 26
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
...doing something funny wrong. (And yeah, tons of >> missed optimization opportunities in this code, but let's not dwell on >> that.) >> >> This is the piglit test: >> >> http://cgit.freedesktop.org/piglit/tree/tests/spec/arb_tessellation_shader/execution/quads.shader_test >> >> It should be noted that other piglit tests don't exhibit this error, >> however they also tend to be simpler. One key difference is that they >> don't change the patch size in TCS. I'm including a link to a text >> file with the tessellation control a...
2014 May 29
2
[PATCH 2/4] nvc0/ir: Handle reverse subop for OP_EXTBF when folding constant expressions
Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp index 58092f4..93f7c2a 100644 ---
2017 Jul 31
1
[RFC PATCH] nv50/ir: allow spilling of def values for constrained MERGES/UNIONS
This lets us spill more values and compile a big shader for Civilization 6. Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_ra.cpp index b33d7b4010..f29c8a1a95
2013 Aug 20
5
[Bug 68344] New: [piglit] shaders/glsl-fs-texture2d-dependent-4 randomly passes or fails on NVAA/NV50
https://bugs.freedesktop.org/show_bug.cgi?id=68344 Priority: medium Bug ID: 68344 Assignee: nouveau at lists.freedesktop.org Summary: [piglit] shaders/glsl-fs-texture2d-dependent-4 randomly passes or fails on NVAA/NV50 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified
2015 Jun 07
43
[Bug 90887] New: PhiMovesPass in register allocator broken
https://bugs.freedesktop.org/show_bug.cgi?id=90887 Bug ID: 90887 Summary: PhiMovesPass in register allocator broken Product: Mesa Version: git Hardware: All OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at