From: Richard Guenther <richard.guenther@gmail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>, gcc@gcc.gnu.org
Subject: Re: FAIL: gcc.c-torture/compile/20000804-1.c -O0 with PIC on gcc-4_4-branch
Date: Mon, 13 Jul 2009 07:32:00 -0000 [thread overview]
Message-ID: <84fc9c000907130032k93fd677o21f6e0ffa5ea62fc@mail.gmail.com> (raw)
In-Reply-To: <20090713033940.GA16166@bromo.med.uc.edu>
On Mon, Jul 13, 2009 at 5:39 AM, Jack Howarth<howarth@bromo.med.uc.edu> wrote:
> 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<howarth@bromo.med.uc.edu> wrote:
>> >> 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 -O0 (test for excess errors)
>>
>> 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
>> > statement to force a 'long long' (64-bits) to go in a register. */
>> > /* { dg-do assemble } */
>> > /* { dg-skip-if "" { { i?86-*-* x86_64-*-* } && ilp32 } { "-fpic" "-fPIC" } { ""
>> > } } */
>> > /* { 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 ()
>> > {
>> > int i[99];
>> > __complex__ long long v;
>> >
>> > v += f ();
>>
>> Undefined behaviour, no?
>>
>> cheers,
>> 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* } && ilp32 } { "*" } { "" } } */
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.
>
>
>
next prev parent reply other threads:[~2009-07-13 7:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 19:41 Jack Howarth
2009-07-12 19:55 ` Richard Guenther
2009-07-12 20:25 ` Jack Howarth
2009-07-13 0:40 ` Dave Korn
2009-07-13 3:39 ` Jack Howarth
2009-07-13 7:32 ` Richard Guenther [this message]
2009-07-13 8:18 ` Dave Korn
2009-07-13 8:23 ` Richard Guenther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84fc9c000907130032k93fd677o21f6e0ffa5ea62fc@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.med.uc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).