From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6246 invoked by alias); 13 Jul 2009 07:32:51 -0000 Received: (qmail 6235 invoked by uid 22791); 13 Jul 2009 07:32:50 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-vw0-f198.google.com (HELO mail-vw0-f198.google.com) (209.85.212.198) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 13 Jul 2009 07:32:43 +0000 Received: by vwj36 with SMTP id 36so1688700vwj.0 for ; Mon, 13 Jul 2009 00:32:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.97.210 with SMTP id m18mr6675609vcn.50.1247470361519; Mon, 13 Jul 2009 00:32:41 -0700 (PDT) In-Reply-To: <20090713033940.GA16166@bromo.med.uc.edu> References: <20090712194138.GA9466@bromo.med.uc.edu> <84fc9c000907121255ye67ec82ld8d23aff790157f@mail.gmail.com> <4A5A8563.2070100@gmail.com> <20090713033940.GA16166@bromo.med.uc.edu> Date: Mon, 13 Jul 2009 07:32:00 -0000 Message-ID: <84fc9c000907130032k93fd677o21f6e0ffa5ea62fc@mail.gmail.com> Subject: Re: FAIL: gcc.c-torture/compile/20000804-1.c -O0 with PIC on gcc-4_4-branch From: Richard Guenther To: Jack Howarth Cc: Dave Korn , gcc@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00213.txt.bz2 On Mon, Jul 13, 2009 at 5:39 AM, Jack Howarth wro= te: > On Mon, Jul 13, 2009 at 01:52:51AM +0100, Dave Korn wrote: >> Richard Guenther wrote: >> > On Sun, Jul 12, 2009 at 9:41 PM, Jack Howarth wrote: >> >> =A0 I am seeing a new failure on x86_64-apple-darwin10 in current gcc= 4.4 branch >> >> that wasn't present in the gcc 4.4.0 release. At -m32, the testsuite = failure... >> >> >> >> FAIL: gcc.c-torture/compile/20000804-1.c =A0-O0 =A0(test for excess e= rrors) >> >> =A0 Do you know what this test is supposed to be doing? >> >> > $ cat /gnu/gcc/gcc/gcc/testsuite/gcc.c-torture/compile/20000804-1.c >> > /* This does not work on m68hc11 or h8300 due to the use of an asm >> > =A0 =A0statement to force a 'long long' (64-bits) to go in a register.= =A0*/ >> > /* { dg-do assemble } */ >> > /* { dg-skip-if "" { { i?86-*-* x86_64-*-* } && ilp32 } { "-fpic" "-fP= IC" } { "" >> > =A0} } */ >> > /* { dg-skip-if "PIC default" { i?86-*-darwin* } { "*" } { "" } } */ >> > /* { dg-skip-if "No 64-bit registers" { m32c-*-* } { "*" } { "" } } */ >> > /* { dg-xfail-if "" { m6811-*-* m6812-*-* h8300-*-* } { "*" } { "" } }= */ >> > >> > /* Copyright (C) 2000, 2003 Free Software Foundation */ >> > __complex__ long long f () >> > { >> > =A0 int i[99]; >> > =A0 __complex__ long long v; >> > >> > =A0 v +=3D f (); >> >> =A0 Undefined behaviour, no? >> >> =A0 =A0 cheers, >> =A0 =A0 =A0 DaveK > > So then the testcase is flawed and should have the darwin line corrected = to... > > /* { dg-skip-if "PIC default" { { i?86-*-darwin* x86_64-*-darwin* } && il= p32 } =A0{ "*" } { "" } } */ Probably yes. The testcase invokes undefined behavior because v is used uninitialized - but that may be the trigger for the original ICE, so better preserve that. Richard. > > >