From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ac131313@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Add "compiler_info"
Date: Sat, 15 Nov 2003 04:50:00 -0000 [thread overview]
Message-ID: <20031115045038.0678B4B3FA@berman.michael-chastain.com> (raw)
I like the copyright notices!
The idea looks sound to me, but I'm a bit too tired to proofread
and test it tonight.
We've already got several places in the test suite
(gdb.base/complex.exp and gdb.base/constvars.exp) that test gcc_compiled
for "2" versus "3" and that machinery is causing no trouble.
Michael C
===
2003-11-14 Andrew Cagney <cagney@redhat.com>
* lib/gdb.exp (compiler_info): New global.
(test_compiler_info): New function.
(get_compiler_info): Set compiler_info.
* lib/compiler.c, lib/compiler.cc: Add copyright. When GNUC, set
"compiler_info".
next reply other threads:[~2003-11-15 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 4:50 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 18:50 Michael Elizabeth Chastain
2003-11-16 16:08 Michael Elizabeth Chastain
2003-11-17 15:04 ` Andrew Cagney
2003-11-17 15:17 ` Andrew Cagney
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=20031115045038.0678B4B3FA@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=ac131313@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