From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 40034] New: E-350 misprocesses shader
Date: Fri, 12 Aug 2011 01:13:59 -0700 (PDT) [thread overview]
Message-ID: <bug-40034-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=40034
Summary: E-350 misprocesses shader
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: curaga@operamail.com
Created an attachment (id=50154)
--> (https://bugs.freedesktop.org/attachment.cgi?id=50154)
Screenshot of the failure
If you pull from my e350bug branch (
http://cgit.freedesktop.org/~cand/mesa/log/?h=e350bug ) and execute
"pp_jimenezmlaa=8 glxgears", you should see a fully white window. What actually
happens on the E-350 is attached.
The gist is "a long shader; output = white;", which should always create white,
since the shader has no kilp/discard. While this would rarely happen in
practise (the glsl compiler would eliminate dead code), this is a clear bug,
and I believe this is causing me other grief.
While the branch is based on ~4 weeks old master, the bug is present when
merged with today's master.
The kernel I'm on is 3.0.1.
--
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:[~2011-08-12 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 8:13 bugzilla-daemon [this message]
2011-08-12 8:14 ` [Bug 40034] E-350 misprocesses shader bugzilla-daemon
2011-08-16 11:21 ` bugzilla-daemon
2011-08-16 11:50 ` bugzilla-daemon
2011-08-16 12:04 ` bugzilla-daemon
2011-08-16 12:52 ` bugzilla-daemon
2011-11-04 16:27 ` bugzilla-daemon
2011-11-07 9:19 ` bugzilla-daemon
2011-11-08 13:06 ` bugzilla-daemon
2012-01-24 13:58 ` bugzilla-daemon
2012-01-24 15:11 ` bugzilla-daemon
2012-01-27 10:56 ` 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-40034-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox