From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62756] Rendering errors on rv790 with llvm and unigine heaven 3.0
Date: Tue, 02 Apr 2013 20:32:15 +0000 [thread overview]
Message-ID: <bug-62756-502-OPLFrJV9jI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62756-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62756
--- Comment #5 from vincent <vljn@ovi.com> ---
No, I don't receive mail from bugzilla until someone add me manually to the cc
list (dont know what to do to fix that though)
I'm aware of the regression with latest HEAD, I'm working on a fix.
r600g still adds CF_ALU on its own which break CF_CLAUSE address natively
encoded by llvm.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1240 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-04-02 20:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 11:07 [Bug 62756] New: Rendering errors on rv790 with llvm and unigine heaven 3.0 bugzilla-daemon
2013-03-26 11:08 ` [Bug 62756] " bugzilla-daemon
2013-03-26 12:01 ` bugzilla-daemon
2013-03-27 11:04 ` bugzilla-daemon
2013-04-02 10:09 ` bugzilla-daemon
2013-04-02 17:12 ` bugzilla-daemon
2013-04-02 20:32 ` bugzilla-daemon [this message]
2013-04-02 21:23 ` bugzilla-daemon
2013-04-03 16:54 ` bugzilla-daemon
2013-04-03 18:47 ` bugzilla-daemon
2013-04-05 15:23 ` bugzilla-daemon
2013-04-05 18:56 ` bugzilla-daemon
2013-04-06 16:15 ` bugzilla-daemon
2013-04-06 18:44 ` bugzilla-daemon
2013-04-24 17:15 ` 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-62756-502-OPLFrJV9jI@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