From: Mike Stump <mikestump@comcast.net>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Janis Johnson <janisjo@codesourcery.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite] skip ARM tests with conflicting options
Date: Wed, 08 Jun 2011 19:39:00 -0000 [thread overview]
Message-ID: <FDC660F8-5C0D-4FA8-B73D-0D5971981EE3@comcast.net> (raw)
In-Reply-To: <4DEF516C.7060703@arm.com>
On Jun 8, 2011, at 3:39 AM, Richard Earnshaw wrote:
> I'm worried by this whole approach of command-line checking.
Right, and this was essentially my point originally. Luckily there is enough beef I think behind the curtains to do everything that needs doing without worrying about adding yet more infrastructure.
> Perhaps a better approach would be a new dg- test
A new mechanism would be necessary if the existing ones turn out to be poor or unworkable. To be concrete, could you give a specific example of something that doesn't work well with the existing mechanisms?
next prev parent reply other threads:[~2011-06-08 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 21:12 Janis Johnson
2011-06-07 21:20 ` Joseph S. Myers
2011-06-07 22:25 ` Janis Johnson
2011-06-07 23:37 ` Janis Johnson
2011-06-08 2:03 ` Mike Stump
2011-06-08 2:54 ` Janis Johnson
2011-06-08 11:47 ` Richard Earnshaw
2011-06-08 16:13 ` Janis Johnson
2011-06-08 19:34 ` Mike Stump
2011-06-08 20:51 ` Janis Johnson
2011-06-08 19:39 ` Mike Stump [this message]
2011-06-10 0:11 ` Janis Johnson
2011-06-10 10:12 ` Richard Earnshaw
2011-06-10 16:22 ` Janis Johnson
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=FDC660F8-5C0D-4FA8-B73D-0D5971981EE3@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@codesourcery.com \
--cc=joseph@codesourcery.com \
--cc=rearnsha@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).