Piglit glsl-fs-discard-02 fails with r300g since: 10937e651222501c0e9f4f44e6b842c261e2edfb is the first bad commit commit 10937e651222501c0e9f4f44e6b842c261e2edfb Author: Vincent Lejeune <vljn@ovi.com> Date: Mon Jan 2 20:17:38 2012 +0100 glsl_to_tgsi: Use the GLSL compiler's new remove-output-reads pass. The existing glsl_to_tgsi::remove_output_read pass did not work properly when indirect addressing was involved; this commit replaces it with a lowering pass that occurs before TGSI code generation. Fixes varying-array related piglit tests. Signed-off-by: Vincent Lejeune <vljn@ovi.com> Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Signed-off-by: Dave Airlie <airlied@redhat.com> GPU: RV530 Mesa: df1cd55ebf362948788c04d2fa7da55c80991605 Kernel: 3.2.3 Libdrm: 2.4.31
Hi, could you please provide the error output for this test, and the generated opcodes using RADEON_DEBUG=fp,vp envar ? RADEON_DEBUG /path/to/piglit/bin/glsl-fs-discard-02 Regards, Vincent
Created attachment 56987 [details] RADEON_DEBUG=fp,vp log
Created attachment 57003 [details] [review] Possible fix Can you try this patch? If it doesn't work can you get the debug output (RADEON_DEBUG=fp,vp) from when the test was passing?
Created attachment 57014 [details] RADEON_DEBUG=fp,vp log (piglit pass) The patch doesn't help. Attaching a new log with 6d4b35c03619148cde89bc5eedaac3288001edd3 (right before the regression).
I'm guessing that this is a bug in the vertex shader. Does running with RADEON_NO_TCL=1 fix it?
(In reply to comment #5) > I'm guessing that this is a bug in the vertex shader. Does running with RADEON_NO_TCL=1 fix it? Yes, the test pass with RADEON_NO_TCL=1 set.
Created attachment 57507 [details] [review] Output remove less aggressive patch Can you try this patch ?
(In reply to comment #7) > Created attachment 57507 [details] [review] [review] > Output remove less aggressive patch > > Can you try this patch ? Yes, that fixes it.
Fixed in git commit b2df031a959f36743527b9abc89913ce4f895de3
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.