From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Fernando Nasser <fnasser@redhat.com>,
gdb-patches@sources.redhat.com,
Daniel Jacobowitz <drow@mvista.com>
Subject: Re: [rfa] store.exp failures
Date: Fri, 06 Dec 2002 14:08:00 -0000 [thread overview]
Message-ID: <3DF11CD6.8010407@redhat.com> (raw)
In-Reply-To: <ro1bs3yvs1f.fsf@jackfruit.Stanford.EDU>
> On Fri, 06 Dec 2002 14:37:32 -0500, Andrew Cagney <ac131313@redhat.com> said:
>
>
>> Thanks. In case you're wondering, yes it does pass but with older
>> compilers.
>
>
> Do you see the two failures with GCC 2.95.3 that I see, by the way?
> They're
>
> FAIL: gdb.base/store.exp: new up struct 1
> FAIL: gdb.base/store.exp: new up struct 2
>
> I don't know if they're our fault or GCC's fault. (Or even nobody's
> fault: the test seems a bit delicate.)
On a powerpc:
Running /home/scratch/GDB/src/gdb/testsuite/gdb.base/store.exp ...
=== gdb Summary ===
# of expected passes 204
ac131313@nettle$ gcc --version
2.95.3
And on a Red Hat 7,2 system:
Running /home/cagney/GDB/src/gdb/testsuite/gdb.base/store.exp ...
=== gdb Summary ===
# of expected passes 204
cagney@torrens$ gcc --version
2.96
>> I'm also wondering of GCC eliminating functions when -O0 is a bug.
>
>
> Yeah, I wondered about that, too: it's not going to make our lives any
> easier if GCC continues doing this...
Asked a GCC engineer. They agreed, at -O0, it shouldn't be eliminating
static functions.
Andrew
next prev parent reply other threads:[~2002-12-06 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 15:32 David Carlton
2002-12-05 16:19 ` Fernando Nasser
2002-12-06 11:37 ` David Carlton
2002-12-06 11:58 ` Andrew Cagney
2002-12-06 12:15 ` David Carlton
2002-12-06 14:08 ` Andrew Cagney [this message]
2002-12-06 19:32 ` David Carlton
2002-12-06 15:54 ` Andrew Cagney
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=3DF11CD6.8010407@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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