From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75276] Implement VGPR Register Spilling
Date: Tue, 29 Jul 2014 03:31:48 +0000 [thread overview]
Message-ID: <bug-75276-502-bGMF5Rjb2j@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75276-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75276
--- Comment #33 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #32)
> > No, that sounds like bug 81834.
>
> So I built mesa with debug symbols and I guess debugging enables some
> assertions because now fails at some assertion about Register.Index stuff.
Yep, that looks like bug 81834. I'm actually not sure why I'm not failing the
assertion in Mesa before the one in LLVM.
> (bug 81834 doesn't say what versions he uses.
I normally use current Git of everything.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2001 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-07-29 3:31 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 18:56 [Bug 75276] New: Implement VGPR Register Spilling bugzilla-daemon
2014-02-20 18:57 ` [Bug 75276] " bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-24 17:45 ` bugzilla-daemon
2014-03-04 6:47 ` bugzilla-daemon
2014-03-04 6:51 ` bugzilla-daemon
2014-04-17 13:11 ` bugzilla-daemon
2014-04-28 18:46 ` bugzilla-daemon
2014-04-28 20:51 ` bugzilla-daemon
2014-04-29 21:36 ` bugzilla-daemon
2014-05-13 15:00 ` bugzilla-daemon
2014-05-16 19:27 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:03 ` bugzilla-daemon
2014-05-17 3:11 ` bugzilla-daemon
2014-05-17 8:37 ` bugzilla-daemon
2014-05-17 12:40 ` bugzilla-daemon
2014-05-17 14:54 ` bugzilla-daemon
2014-05-17 17:40 ` bugzilla-daemon
2014-05-17 17:41 ` bugzilla-daemon
2014-05-17 18:44 ` bugzilla-daemon
2014-05-18 0:32 ` bugzilla-daemon
2014-05-18 0:37 ` bugzilla-daemon
2014-05-18 10:41 ` bugzilla-daemon
2014-05-19 13:50 ` bugzilla-daemon
2014-05-19 13:50 ` bugzilla-daemon
2014-05-19 22:51 ` bugzilla-daemon
2014-06-16 17:08 ` bugzilla-daemon
2014-06-28 9:58 ` bugzilla-daemon
2014-07-03 21:20 ` bugzilla-daemon
2014-07-13 4:33 ` bugzilla-daemon
2014-07-24 11:58 ` bugzilla-daemon
2014-07-28 10:08 ` bugzilla-daemon
2014-07-28 11:10 ` bugzilla-daemon
2014-07-29 3:31 ` bugzilla-daemon [this message]
2014-07-29 3:33 ` bugzilla-daemon
2014-08-28 12:15 ` bugzilla-daemon
2014-08-28 12:19 ` bugzilla-daemon
2014-08-28 12:21 ` bugzilla-daemon
2014-08-29 7:19 ` bugzilla-daemon
2014-09-07 13:28 ` bugzilla-daemon
2014-09-07 16:10 ` bugzilla-daemon
2014-09-07 16:12 ` bugzilla-daemon
2014-09-07 20:21 ` bugzilla-daemon
2014-09-13 17:39 ` bugzilla-daemon
2014-09-17 6:55 ` bugzilla-daemon
2014-09-19 1:11 ` bugzilla-daemon
2014-09-19 23:58 ` bugzilla-daemon
2014-09-20 9:01 ` bugzilla-daemon
2014-09-24 17:11 ` bugzilla-daemon
2014-09-25 20:38 ` bugzilla-daemon
2014-09-26 17:16 ` bugzilla-daemon
2014-11-08 9:55 ` bugzilla-daemon
2014-11-10 14:34 ` bugzilla-daemon
2014-11-11 1:38 ` bugzilla-daemon
2014-11-21 10:24 ` bugzilla-daemon
2015-01-07 22:10 ` bugzilla-daemon
2015-01-08 7:48 ` bugzilla-daemon
2015-01-09 20:18 ` bugzilla-daemon
2015-01-13 19:12 ` bugzilla-daemon
2015-01-13 19:15 ` bugzilla-daemon
2015-01-13 19:18 ` bugzilla-daemon
2015-02-05 15:52 ` bugzilla-daemon
2015-02-05 15:56 ` 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-75276-502-bGMF5Rjb2j@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;
as well as URLs for NNTP newsgroup(s).