From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc;testsuite] Append patchlevel to compiler_info
Date: Wed, 09 Jun 2004 19:34:00 -0000 [thread overview]
Message-ID: <40C76632.7060308@gnu.org> (raw)
In-Reply-To: <20040609192405.712044B104@berman.michael-chastain.com>
> 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.
True.
> Can you do a before-and-after test with gcc 2.95.3 and with some
> version of gcc 3.X ?
I've already done that.
> 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.
I was thinking more of changing ``gcc-*-*'' to ``gcc-*''.
> 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-".
It works as is, however I can append "-unknown" - I suspect that's
better than the ucase "-UNKNOWN".
Andrew
next prev parent reply other threads:[~2004-06-09 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 19:24 Michael Elizabeth Chastain
2004-06-09 19:34 ` Andrew Cagney [this message]
-- 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=40C76632.7060308@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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