From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29767 invoked by alias); 13 Feb 2004 17:49:51 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 29750 invoked by uid 48); 13 Feb 2004 17:49:42 -0000 Date: Fri, 13 Feb 2004 17:49:00 -0000 Message-ID: <20040213174942.29749.qmail@sources.redhat.com> From: "stefaan dot simoens at tiscali dot be" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040206230200.14053.stefaan.simoens@tiscali.be> References: <20040206230200.14053.stefaan.simoens@tiscali.be> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug optimization/14053] second stage build errors (--with-cpu=601) X-Bugzilla-Reason: CC X-SW-Source: 2004-02/txt/msg01422.txt.bz2 List-Id: ------- Additional Comments From stefaan dot simoens at tiscali dot be 2004-02-13 17:49 ------- I did a "make check-gcc" both with and without -mcpu=601 in the RUNTESTFLAGS (the testsuite from the latest gcc-3.3.3-20040210 snapshot; I haven't compiled gcc-3.3.3 yet but the problem with -mcpu=601 exists in my current 3.3.1 compiler als well) The test with arith-math-ll.c was the only one who failed with the -mcpu=601 optimization, it passes without -mcpu=601. I think it's easier to look where the error comes is right now? (I'm not sure it's a math problem though; apparently arith-math-ll.c is the only test which triggers the problem on execution... (I'll compile gcc-3.3.3-20040210 (without -mcpu=601) and re-run the tests so you have an up-to-date view on the facts -- but i'm not sure "-mcpu=601" changed much between 3.3.1 and 3.3.3?) Good luck... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14053