From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, gdb-patches@sources.redhat.com, mec.gnu@mindspring.com
Subject: Re: [patch/rfc;testsuite] Append patchlevel to compiler_info
Date: Wed, 09 Jun 2004 19:24:00 -0000 [thread overview]
Message-ID: <20040609192405.712044B104@berman.michael-chastain.com> (raw)
This is good. I think it needs a comment that gcc supports
__GNUC_PATCHLEVEL__ starting with gcc 3.0, so that we know how long
we need to keep the conditional logic.
Can you do a before-and-after test with gcc 2.95.3 and with some
version of gcc 3.X ? I expect that all the "gcc-2-*" and "gcc-*-*"
will continue to work but that really needs testing. They can be
improved to "gcc-2-*-*" and "gcc-*-*-*" later.
Hmmm, come to think of it, I don't know if "gcc-*-*-*" will match
"gcc-2-95-". How about if you make the unknown case "gcc-X-Y-UNKNOWN"
instead of "gcc-X-Y-".
Michael C
2004-06-09 Andrew Cagney <cagney@gnu.org>
* lib/compiler.cc, lib/compiler.c: Append __GNUC_PATCHLEVEL__ to
the compiler_info.
* gdb.base/structs.exp (test_struct_calls): Check for gcc-3-3-*
instead of gcc-3-3.
next reply other threads:[~2004-06-09 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 19:24 Michael Elizabeth Chastain [this message]
2004-06-09 19:34 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-06-10 19:25 Michael Elizabeth Chastain
2004-06-10 21:39 ` Andrew Cagney
2004-06-09 20:09 Michael Elizabeth Chastain
2004-06-10 19:17 ` Andrew Cagney
2004-06-09 17:46 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=20040609192405.712044B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--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