From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/stabs] weird.exp: skip hp
Date: Thu, 08 Jan 2004 00:40:00 -0000 [thread overview]
Message-ID: <20040108004053.C191A4B35A@berman.michael-chastain.com> (raw)
ac> BTW, does your get_compiler_info rewrite mean that those hpcc_...
ac> variables can eventually be eliminated (replaced by test_compiler_info)?
Hell yeah!
In fact, get_compiler_info logs the value that it calculates for
"compiler_info". gdb.log looks like this:
Running /house/chastain/gdb/s1/gdb/testsuite/gdb.base/volatile.exp ...
get_compiler_info: hpcc-111106
Executing on host: gcc /house/chastain/gdb/s1/gdb/testsuite/gdb.base/constvars.c -g -lm -o /house/chastain/gdb/build/hppa2.0w-hp-hpux11.11/s1-blank-gcc/gdb/testsuite/gdb.base/constvars (timeout = 300)
GNU gdb 2004-01-07-cvs
Copyright 2004 Free Software Foundation, Inc.
(Yes, my hpcc compiler is a shell script named "gcc").
And it will be trivial to add more vendor compilers to
compiler.c/compiler.cc:
#if defined(__SUN_whatever)
set compiler_info [join {suncc __SUN_whatever} -]
#endif
#if defined(__TRU64_blah)
set compiler_info [join {osfcc __TRU64_blah} -]
#endif
Michael C
next reply other threads:[~2004-01-08 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 0:40 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 21:59 Michael Elizabeth Chastain
2004-01-07 21:31 Michael Elizabeth Chastain
2004-01-07 21:38 ` Elena Zannoni
2004-01-07 23:59 ` 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=20040108004053.C191A4B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=ezannoni@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