From: Janis Johnson <janis_johnson@mentor.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <rearnsha@arm.com>
Subject: PING: gcc.target/arm: skip 5 tests for flag conflicts
Date: Mon, 14 Jan 2013 21:21:00 -0000 [thread overview]
Message-ID: <50F47710.4020800@mentor.com> (raw)
Richard,
Back in September I submitted a patch to fix five ARM tests in
<http://gcc.gnu.org/ml/gcc-patches/2012-09/msg01515.html>.
You responded in < http://gcc.gnu.org/ml/gcc-patches/2012-10/msg00972.html>
and I answered your questions in a reply.
The first of the modified tests doesn't need to be changed, at least for
the sets of flags with which I usually test, but the others all conflict
with some of my multilib flags. Note that the tests will be run with
the specified options for a default multilib, or one that doesn't use
any of the same options that are needed for the multilib.
Can I check those in now?
Janis
next reply other threads:[~2013-01-14 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 21:21 Janis Johnson [this message]
2013-01-16 13:35 Nick Clifton
2013-01-16 23:47 ` Janis Johnson
2013-01-17 15:04 ` nick clifton
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=50F47710.4020800@mentor.com \
--to=janis_johnson@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@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).