From: nick clifton <nickc@redhat.com>
To: janisjo@codesourcery.com
Cc: Janis Johnson <janis_johnson@mentor.com>,
gcc-patches@gcc.gnu.org, rearnshaw@cambridge.arm.com
Subject: Re: PING: gcc.target/arm: skip 5 tests for flag conflicts
Date: Thu, 17 Jan 2013 15:04:00 -0000 [thread overview]
Message-ID: <50F811FA.6070508@redhat.com> (raw)
In-Reply-To: <50F73C8B.6040700@mentor.com>
Hi Janis,
> Now I get it. This version is more selective about which multilibs
> are skipped. I tested it by using multilib test flags for all valid
> values for -march, with and without -mthumb as appropriate for the
> arch. The ones that are now skipped are the ones that used to fail
> with complaints from the compiler.
>
> Is this OK?
Approved - please apply - thanks for persevering with this.
Cheers
Nick
next prev parent reply other threads:[~2013-01-17 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:35 Nick Clifton
2013-01-16 23:47 ` Janis Johnson
2013-01-17 15:04 ` nick clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 21:21 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=50F811FA.6070508@redhat.com \
--to=nickc@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janis_johnson@mentor.com \
--cc=janisjo@codesourcery.com \
--cc=rearnshaw@cambridge.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).