From: Andrew Cagney <ac131313@redhat.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Add "compiler_info"
Date: Mon, 17 Nov 2003 15:17:00 -0000 [thread overview]
Message-ID: <3FB8E691.8090409@redhat.com> (raw)
In-Reply-To: <3FB8E394.6030801@redhat.com>
> Yea, the macro's GNUC but if if you asked anyone the would say GCC. Changed and committed.
> The now redundant "gcc_compiled" should probably get expunged.
PS: Just ignore my accidental commit of structs.{c,exp}, I've reverted it.
Andrew
next prev parent reply other threads:[~2003-11-17 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 16:08 Michael Elizabeth Chastain
2003-11-17 15:04 ` Andrew Cagney
2003-11-17 15:17 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 18:50 Michael Elizabeth Chastain
2003-11-15 4:50 Michael Elizabeth Chastain
2003-11-14 22:50 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=3FB8E691.8090409@redhat.com \
--to=ac131313@redhat.com \
--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