From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1317 invoked by alias); 30 Jan 2003 04:27:08 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 1310 invoked from network); 30 Jan 2003 04:27:07 -0000 Received: from unknown (HELO vitelus.com) (64.81.243.207) by 172.16.49.205 with SMTP; 30 Jan 2003 04:27:07 -0000 Received: from aaronl by vitelus.com with local (Exim 3.36 #1 (Debian)) id 18e6Fd-0007qH-00; Wed, 29 Jan 2003 20:24:33 -0800 Date: Thu, 30 Jan 2003 09:20:00 -0000 From: Aaron Lehmann To: doko@debian.org, gcc@gcc.gnu.org Subject: GCC 3.2.x miscompiles X Message-ID: <20030130042433.GO18700@vitelus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i X-SW-Source: 2003-01/txt/msg01629.txt.bz2 In the unstable branch of Debian, a bug has recently been introduced which breaks hardware-accelerated GL for Radeon users on ia32. The bug report is at http://bugs.debian.org/178242. This one hit me particularly hard, as I have a Radeon in both my laptop and my desktop. A comment in the bug report linked the problem to GCC, so I attempted to compile Debian's XFree86 packages with today's GCC mainline. Sure enough, this fixed the bug. http://marc.theaimsgroup.com/?l=dri-devel&m=103851238913228 suggests that the problem is the fault of GCC mixing FPU code with MMX code. The same message implies that this has been fixed in GCC 3.2.1, but I was able to reproduce this bug in GCC 3.2.2 20030124 (Debian prerelease). Since this problem seems to have been fixed in HEAD, and possibly in the 3.3 branch (I haven't tested it), I'm wondering if anyone can point me towards the patch that fixed the bug. I looked in GNATS but was not able to find an associated PR. I'm sorry that I can't provide a worthwhile testcase at this point, only a vague hypothesis about the problem. Thanks, Aaron Lehmann Debian Developer