From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63632] mesa +r600 llvm = segfault
Date: Mon, 22 Apr 2013 21:56:38 +0000 [thread overview]
Message-ID: <bug-63632-502-0mO2Oq39Pz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63632-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63632
--- Comment #4 from Tom Stellard <tstellar@gmail.com> ---
(In reply to comment #3)
> (In reply to comment #2)
> > I can't reproduce this with LLVM r179895 and Mesa
> > 12eab7cc564a6928197f9b87ded9e368e56976f0
> >
> > Have you done full rebuilds of both projects?
>
> Yes, I always do make [dist]clean and git clean -dfx.
>
> I have just deleted both trees and re-cloned to be sure, but the segfault is
> still there.
>
> When I was on my working commits moving either llvm or mesa to head while
> keeping the other on "working" produced the segfault (which is why I didn't
> do a proper bisect).
>
> I always clean and rebuild mesa after llvm has changed.
I was able to reproduce this on my gentoo system, but not on either of my
fedora systems. I will investigate further, what distro are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1838 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-22 21:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 9:56 [Bug 63632] New: RS880 + mesa/llvm heads - segfault bugzilla-daemon
2013-04-19 21:55 ` [Bug 63632] mesa +r600 llvm = segfault bugzilla-daemon
2013-04-20 6:07 ` bugzilla-daemon
2013-04-20 9:48 ` bugzilla-daemon
2013-04-22 21:56 ` bugzilla-daemon [this message]
2013-04-22 23:06 ` bugzilla-daemon
2013-04-23 9:13 ` bugzilla-daemon
2013-04-23 14:32 ` bugzilla-daemon
2013-04-23 19:00 ` bugzilla-daemon
2013-04-23 19:05 ` bugzilla-daemon
2013-04-23 19:08 ` bugzilla-daemon
2013-04-23 19:28 ` bugzilla-daemon
2013-04-23 20:26 ` bugzilla-daemon
2013-04-24 7:46 ` bugzilla-daemon
2013-04-24 10:47 ` bugzilla-daemon
2013-04-27 14:27 ` 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-63632-502-0mO2Oq39Pz@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