From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73320] [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation
Date: Mon, 13 Jan 2014 19:23:11 +0000 [thread overview]
Message-ID: <bug-73320-502-fvFuHJ635b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73320-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 401 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73320
--- Comment #2 from Tom Stellard <tstellar@gmail.com> ---
Are you using the released version of LLVM 3.4 or an older git snapshot? If
you are using the released version of LLVM 3.4, can you run the game with the
environment variable: R600_DEBUG=ps,vs and post the output?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1273 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:[~2014-01-13 19:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 12:42 [Bug 73320] New: [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation bugzilla-daemon
2014-01-13 8:56 ` [Bug 73320] " bugzilla-daemon
2014-01-13 19:23 ` bugzilla-daemon [this message]
2014-01-13 19:51 ` bugzilla-daemon
2014-01-23 5:54 ` bugzilla-daemon
2014-01-23 5:56 ` bugzilla-daemon
2014-01-31 18:04 ` bugzilla-daemon
2014-02-07 23:32 ` bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-22 6:20 ` bugzilla-daemon
2014-02-22 6:20 ` bugzilla-daemon
2014-02-22 17:59 ` bugzilla-daemon
2014-02-24 17:48 ` bugzilla-daemon
2014-02-25 17:30 ` bugzilla-daemon
2014-02-26 22:39 ` bugzilla-daemon
2014-02-27 6:57 ` bugzilla-daemon
2014-03-02 10:26 ` bugzilla-daemon
2014-03-02 19:20 ` bugzilla-daemon
2014-03-03 19:53 ` bugzilla-daemon
2014-03-04 7:10 ` bugzilla-daemon
2014-03-05 21:55 ` bugzilla-daemon
2014-03-05 22:12 ` bugzilla-daemon
2014-03-06 22:37 ` bugzilla-daemon
2014-03-29 18:33 ` bugzilla-daemon
2014-04-03 3:03 ` bugzilla-daemon
2014-04-03 3:30 ` bugzilla-daemon
2014-04-03 18:22 ` bugzilla-daemon
2014-04-03 18:29 ` bugzilla-daemon
2014-04-17 15:52 ` bugzilla-daemon
2014-04-17 15:55 ` bugzilla-daemon
2014-04-17 21:41 ` bugzilla-daemon
2014-04-17 21:47 ` bugzilla-daemon
2014-04-17 22:09 ` bugzilla-daemon
2014-04-17 22:28 ` bugzilla-daemon
2014-04-17 23:01 ` bugzilla-daemon
2014-04-28 14:46 ` bugzilla-daemon
2014-04-28 20:52 ` bugzilla-daemon
2014-04-29 21:36 ` bugzilla-daemon
2014-04-30 19:30 ` bugzilla-daemon
2014-04-30 19:37 ` bugzilla-daemon
2014-04-30 20:39 ` bugzilla-daemon
2014-05-03 19:43 ` bugzilla-daemon
2014-05-04 10:19 ` bugzilla-daemon
2014-05-04 16:50 ` bugzilla-daemon
2014-05-09 22:05 ` bugzilla-daemon
2014-05-09 22:44 ` bugzilla-daemon
2014-05-10 15:42 ` bugzilla-daemon
2014-05-11 0:03 ` bugzilla-daemon
2014-05-11 11:28 ` bugzilla-daemon
2014-05-11 18:43 ` bugzilla-daemon
2014-05-16 19:29 ` bugzilla-daemon
2014-05-16 22:50 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2015-02-06 1:35 ` 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-73320-502-fvFuHJ635b@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