From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43332] corrupted output in mesa-demo/fp-tri using r600g on evergreen
Date: Thu, 15 Dec 2011 17:53:39 +0000 [thread overview]
Message-ID: <bug-43332-502-aPIq6bkmYe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43332-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=43332
--- Comment #3 from Stefano Teso <stefano.teso@gmail.com> 2011-12-15 09:53:39 PST ---
(In reply to comment #2)
> > The bug is also present in the libGL 7.11.2 shipped by debian, so I don't think
> > it's a regression or a bug in my config.
>
> It looks like that inst->Dst[0].Register.WriteMask == 3 in tgsi_scs (), so the
> ZW components of the dest register are never written. Perhaps this could
> explain the artifact. Not that I'm a GL expert or anything ;-)
Forcing the mask to 15 fixes the problem. Of course this is no solution. Likely
the fragment color is not cleared properly before calling SCS?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-12-15 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 11:09 [Bug 43332] New: corrupted output in mesa-demo/fp-tri using r600g on evergreen bugzilla-daemon
2011-11-29 3:10 ` [Bug 43332] " bugzilla-daemon
2011-12-15 17:37 ` bugzilla-daemon
2011-12-15 17:53 ` bugzilla-daemon [this message]
2011-12-16 10:15 ` [Bug 43332] corrupted output in mesa-demo/fp-tri using r600g bugzilla-daemon
2011-12-16 16:46 ` bugzilla-daemon
2011-12-29 17:13 ` 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-43332-502-aPIq6bkmYe@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