From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71647] radeonsi purple tinted colors
Date: Fri, 15 Nov 2013 18:22:48 +0000 [thread overview]
Message-ID: <bug-71647-502-IWBelsULzX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71647-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71647
--- Comment #2 from Tom Stellard <tstellar@gmail.com> ---
Can you bisect this? It's possible that this commit is responsible:
R600/SI: Prefer SALU instructions for bit shift operations
All shift operations will be selected as SALU instructions and then
if necessary lowered to VALU instructions in the SIFixSGPRCopies pass.
This allows us to do more operations on the SALU which will improve
performance and is also required for implementing private memory
using indirect addressing, since the private memory pointers must stay
in the scalar registers.
This patch includes some fixes from Matt Arsenault.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@194625
91177308-0d34-0410-b5e6-96231b3b80d8
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1682 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-15 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:35 [Bug 71647] New: radeonsi purple tinted colors bugzilla-daemon
2013-11-15 14:38 ` [Bug 71647] " bugzilla-daemon
2013-11-15 18:09 ` bugzilla-daemon
2013-11-15 18:11 ` bugzilla-daemon
2013-11-15 18:22 ` bugzilla-daemon [this message]
2013-11-15 19:34 ` bugzilla-daemon
2013-11-15 19:34 ` 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-71647-502-IWBelsULzX@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