From: Timothy Wall <twall@oculustech.com>
To: gdb@sources.redhat.com
Subject: Using a compiler for testsuite that's not GCC?
Date: Mon, 29 Oct 2001 06:13:00 -0000 [thread overview]
Message-ID: <3BDD63C0.FA2CE158@oculustech.com> (raw)
What's the best way to go about this? It seems a lot of the tests assume gcc and so throw gcc-specific options at the compiler. It seems the approach with least effort would be to point dejagnu at a wrapper which translates gcc options into ones the other compiler understands...
T.
next reply other threads:[~2001-10-29 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 6:13 Timothy Wall [this message]
2001-10-29 8:21 ` Andrew Cagney
2001-10-29 9:05 ` Timothy Wall
2001-10-29 9:15 ` Timothy Wall
2001-10-29 9:44 ` Stan Shebs
2001-10-29 10:04 ` Timothy Wall
2001-10-29 20:04 Timothy Wall
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=3BDD63C0.FA2CE158@oculustech.com \
--to=twall@oculustech.com \
--cc=gdb@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