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 11:58:00 -0000 [thread overview]
Message-ID: <3DF0FC7C.6050209@redhat.com> (raw)
In-Reply-To: <ro1r8cvuev2.fsf@jackfruit.Stanford.EDU>
> On Thu, 05 Dec 2002 19:16:54 -0500, Fernando Nasser <fnasser@redhat.com> said:
>
>
>> I don't think not being static affects the goal of test at all, so if
>> it fixes the problem I have no objection.
>
>
> Thanks, I've committed it.
Thanks. In case you're wondering, yes it does pass but with older
compilers. Now we get to see what bugs it flushes out ...
I'm also wondering of GCC eliminating functions when -O0 is a bug.
Andrew
next prev parent reply other threads:[~2002-12-06 19:37 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 [this message]
2002-12-06 12:15 ` David Carlton
2002-12-06 14:08 ` Andrew Cagney
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=3DF0FC7C.6050209@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