From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Problems with dejagnu and c++ tests...
Date: Wed, 04 Feb 2004 14:01:00 -0000 [thread overview]
Message-ID: <20040204140131.D58B14B364@berman.michael-chastain.com> (raw)
Well, you could just add "return 1" to skip_cplus_tests on that system.
But in the long run, get_compiler_info needs to be smarter.
(Really, default_target_compile needs to have a better interface,
but we can't touch that).
Perhaps we should just kill get_compiler_info and add some more
code to initialization. Have it compile and run two test programs,
one in C, and one in C++. Like this:
#include <stdio.h>
int main ()
{
#if defined(__GNUC__)
printf ("set compiler_info gcc-%d-%d\n", __GNUC__, __GNUC__MINOR__);
printf ("set gcc_compiled %d\n", __GNUC__);
else
printf ("set gcc_compiled 0\n")
#endif
}
Then just save the results and have get_compiler_info set the right
results for the language specified.
Michael C
next reply other threads:[~2004-02-04 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 14:01 Michael Elizabeth Chastain [this message]
2004-02-04 15:41 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 23:50 Michael Elizabeth Chastain
2004-02-04 23:55 ` Daniel Jacobowitz
2004-02-04 23:03 Michael Elizabeth Chastain
2004-02-04 23:13 ` Daniel Jacobowitz
2004-02-04 22:31 Michael Elizabeth Chastain
2004-02-04 22:49 ` Andrew Cagney
2004-02-04 12:50 Michael Elizabeth Chastain
2004-02-04 13:20 ` Joel Brobecker
2004-02-04 11:58 Joel Brobecker
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=20040204140131.D58B14B364@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.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