Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Sun, 16 Nov 2003 16:08:00 -0000	[thread overview]
Message-ID: <20031116160805.0D6D14B408@berman.michael-chastain.com> (raw)

Proofread and tested, no problems.  I'm appending a little snippet
of test code.  I tested with:

  gcc 2.95.3		# reports gnuc-2-95
  gcc 3.2-7-rh		# reports gnuc-3-2
  gcc 3.3.2		# reports gnuc-3-3
  gcc gcc-3_3-branch	# reports gnuc-3-3
  gcc HEAD		# reports gnuc-3-4

I didn't test the non-gcc path.

I prefer "gcc" to "gnuc" but "gnuc" is okay by me.

Recommended for approval.

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".

===

global compiler_info
warning "compiler_info: ${compiler_info}"
if [test_compiler_info gnuc-2-*] {
    warning "test_compiler_info: gnuc-2-*"
}
if [test_compiler_info gnuc-3-*] {
    warning "test_compiler_info: gnuc-3-*"
}
if [test_compiler_info gnuc-3-2] {
    warning "test_compiler_info: gnuc-3-2"
}
if [test_compiler_info gnuc-3-3] {
    warning "test_compiler_info: gnuc-3-3"
}
if [test_compiler_info gnuc-3-4] {
    warning "test_compiler_info: gnuc-3-4"
}


             reply	other threads:[~2003-11-16 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 16:08 Michael Elizabeth Chastain [this message]
2003-11-17 15:04 ` Andrew Cagney
2003-11-17 15:17   ` Andrew Cagney
  -- 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=20031116160805.0D6D14B408@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