From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, fnasser@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Test printing complex numbers in C
Date: Wed, 04 Dec 2002 20:29:00 -0000 [thread overview]
Message-ID: <200212050429.gB54T8h31459@duracef.shout.net> (raw)
Fernando Nasser writes:
> I wonder if we wouldn't do something with regards to compiler (GCC)
> versions as well.
I think we should bite the bullet and add something to lib/gdb.exp
to figure out the compiler version.
In fact, I see that we already do! The variable "gcc_compiled" is set
to __GNUC__ if that is defined, or 0 if nothing is defined. "info cpp"
says that __GNUC__ equals the major version of the compiler: 2 for gcc
2.x and 3 for gcc 3.x. This is a documented feature so we can rely on
it being the major version number for all gcc's forever.
So "gcc_compiled" is more than a boolean, it actually has the values:
0 not gnu c
2 gcc v2
3 gcc v3
I haven't actually tested this because I'm kinda tired and my test bed
is cranking on 5.2.91 and I don't want to get close to its playpen
and I don't want to start a different test bed.
As far as using it goes, I agree with Fernando, it's usually a good idea,
because it increases the specificity of the test suite. Also it makes
the test suite a lot easier to maintain because it's clear which results
are expected from which compilers, so that people can read it easier,
and obsolete compilers can be de-supported more easily.
Michael C
next reply other threads:[~2002-12-05 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 20:29 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 8:54 Michael Elizabeth Chastain
2002-12-04 15:19 ` Fernando Nasser
2002-10-04 20:21 Daniel Jacobowitz
2002-12-03 8:24 ` Fernando Nasser
2002-12-03 8:33 ` Daniel Jacobowitz
2002-12-04 15:23 ` Fernando Nasser
2002-12-05 7:10 ` Fernando Nasser
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=200212050429.gB54T8h31459@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=fnasser@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