From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 63632] mesa +r600 llvm = segfault
Date: Sat, 20 Apr 2013 09:48:23 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1121162767=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 924C5E5C14
for ;
Sat, 20 Apr 2013 02:48:23 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1121162767==
Content-Type: multipart/alternative; boundary="1366451303.2b1F0.6749"; charset="us-ascii"
--1366451303.2b1F0.6749
Date: Sat, 20 Apr 2013 09:48:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
https://bugs.freedesktop.org/show_bug.cgi?id=63632
--- Comment #3 from Andy Furniss ---
(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.
--
You are receiving this mail because:
You are the assignee for the bug.
--1366451303.2b1F0.6749
Date: Sat, 20 Apr 2013 09:48:23 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Comment # 3
on bug 63632
from Andy Furniss
(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.
You are receiving this mail because:
- You are the assignee for the bug.
--1366451303.2b1F0.6749--
--===============1121162767==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
--===============1121162767==--