From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GazUp-0005bY-Td
	for qemu-devel@nongnu.org; Fri, 20 Oct 2006 14:53:31 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GazUo-0005Ze-9Q
	for qemu-devel@nongnu.org; Fri, 20 Oct 2006 14:53:31 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GazUn-0005ZM-VI
	for qemu-devel@nongnu.org; Fri, 20 Oct 2006 14:53:30 -0400
Received: from [12.7.175.14] (helo=mx2.palmsource.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GazUo-0003Sv-20
	for qemu-devel@nongnu.org; Fri, 20 Oct 2006 14:53:30 -0400
Message-ID: <45391B22.1050608@palmsource.com>
Date: Fri, 20 Oct 2006 11:53:22 -0700
From: "K. Richard Pixley" <rich.pixley@palmsource.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] qemu vs gcc4
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Could someone please explain the issue with gcc4, please?  Or point me 
to an existing explanation?

I mean, I understand that qemu is believed to be building incorrectly 
with gcc4.  But what is the failure mode folks have been seeing?  And 
what's being done about it or what needs to be done about it?  Is this 
an issue for all targets or is it x86 specific?

Thanks,
--rich