From: David Carlton <carlton@math.stanford.edu>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com, fnasser@redhat.com
Subject: Re: [rfa/testsuite] gdb.base/selftest.exp: work with optimization
Date: Wed, 11 Dec 2002 14:31:00 -0000 [thread overview]
Message-ID: <ro1of7stcmw.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200212112215.gBBMFqh08988@duracef.shout.net>
On Wed, 11 Dec 2002 16:15:52 -0600, Michael Elizabeth Chastain <mec@shout.net> said:
> David Carlton writes:
> + # "current_directory initialization" possibilities happen to
> + # me with GCC 3.1 on i686-pc-linux-gnu when I compile with
> + # optimization.
> That is twice today you said "gcc 3.1" -- is that a think for gcc 3.2.1,
> or are you really testing with gcc 3.1?
I really am testing with GCC 3.1 most of the time: on my work machine,
that's what's installed in /usr/local/bin (though other GCC's are
installed elsewhere, and they sometimes get used).
Obviously it's not the most important version of GCC to test with, but
I haven't yet run into a compelling reason to upgrade to a more recent
version; and it probably doesn't hurt to have somebody testing GDB
with compilers other than 2.95-variants and 3.2.1. (Though your test
matrix now handles that issue quite nicely.) In the comment quoted
above, I have no reason to believe that the problem is specific to
3.1, but it seemed like a situation where it was worthwhile mentioning
the compiler that I happened to be using.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-11 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 14:19 Michael Elizabeth Chastain
2002-12-11 14:31 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 21:52 Michael Elizabeth Chastain
2002-12-11 13:24 David Carlton
2002-12-11 15:22 ` Andrew Cagney
2002-12-22 10:25 ` Fernando Nasser
2002-12-23 9:08 ` David Carlton
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=ro1of7stcmw.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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