From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50999] New: [r300g, bisected] piglit glsl-fs-discard-04 fails
Date: Tue, 12 Jun 2012 02:31:47 +0000 [thread overview]
Message-ID: <bug-50999-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=50999
Bug #: 50999
Summary: [r300g, bisected] piglit glsl-fs-discard-04 fails
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Keywords: regression
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: pavel.ondracka@email.cz
CC: eric@anholt.net, tstellar@gmail.com
Created attachment 62924
--> https://bugs.freedesktop.org/attachment.cgi?id=62924
RADEON_DEBUG=fp log
./bin/shader_runner tests/shaders/glsl-fs-discard-04.shader_test -auto -fbo
Probe at (0,0)
Expected: 0.000000 1.000000 0.000000 0.000000
Observed: 1.000000 0.000000 0.000000 0.000000
PIGLIT: {'result': 'fail' }
Regression test shows:
e21b9f1f19d2345026a7fbe095a776d0b64557ec is the first bad commit
commit e21b9f1f19d2345026a7fbe095a776d0b64557ec
Author: Eric Anholt <eric@anholt.net>
Date: Fri May 4 13:37:08 2012 -0700
glsl: Remove the opt_discard_simplification pass.
This conflicts with the GLSL 1.30+ rules for derivatives after a
discard has occurred.
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
llvmpipe works fine, so this may be another uncovered r300 compiler issue.
GPU:RV530
Kernel: 3.4.0-1.fc17.i686
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-06-12 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 2:31 bugzilla-daemon [this message]
2019-09-18 18:51 ` [Bug 50999] [r300g, bisected] piglit glsl-fs-discard-04 fails bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-50999-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.