From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82828] Regression: Crash in 3Dmark2001
Date: Tue, 02 Sep 2014 18:09:25 +0000 [thread overview]
Message-ID: <bug-82828-502-ozfdiua8RY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82828-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1088 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82828
--- Comment #13 from Tom Stellard <tstellar@gmail.com> ---
(In reply to comment #12)
> Created attachment 105630 [details] [review]
> another debugging patch
>
> Ok, it looks like the problem is that node 0's q_total is bogus, which means
> it never even gets considered for optimistic coloring. To help me figure out
> why this is, can you apply this patch to master (not on top of the other
> patch) and tell me the output of the piglit test now?
On (In reply to comment #12)
> Created attachment 105630 [details] [review]
> another debugging patch
>
> Ok, it looks like the problem is that node 0's q_total is bogus, which means
> it never even gets considered for optimistic coloring. To help me figure out
> why this is, can you apply this patch to master (not on top of the other
> patch) and tell me the output of the piglit test now?
I'm not sure if this matters, but r300g pre-allocates the input registers
before calling ra_allocate_no_spills().
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2575 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-09-02 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 21:11 [Bug 82828] New: Regression: Crash in 3Dmark2001 bugzilla-daemon
2014-08-20 17:01 ` [Bug 82828] " bugzilla-daemon
2014-08-26 13:06 ` bugzilla-daemon
2014-08-29 16:43 ` bugzilla-daemon
2014-08-29 20:06 ` bugzilla-daemon
2014-08-30 7:19 ` bugzilla-daemon
2014-08-30 17:54 ` bugzilla-daemon
2014-08-30 20:50 ` bugzilla-daemon
2014-09-01 10:31 ` bugzilla-daemon
2014-09-01 21:37 ` bugzilla-daemon
2014-09-01 21:39 ` bugzilla-daemon
2014-09-02 6:21 ` bugzilla-daemon
2014-09-02 18:00 ` bugzilla-daemon
2014-09-02 18:09 ` bugzilla-daemon [this message]
2014-09-02 18:23 ` bugzilla-daemon
2014-09-02 18:45 ` bugzilla-daemon
2014-09-02 18:49 ` bugzilla-daemon
2014-09-02 21:09 ` bugzilla-daemon
2014-09-02 21:17 ` bugzilla-daemon
2014-09-03 0:26 ` bugzilla-daemon
2014-09-09 22:46 ` bugzilla-daemon
2014-09-12 9:47 ` bugzilla-daemon
2014-09-12 14:09 ` bugzilla-daemon
2014-09-17 12:11 ` 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-82828-502-ozfdiua8RY@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.