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: replace gcc.target/arm/ftest-*.c with compile-only tests
Date: Mon, 14 Jan 2013 21:28:00 -0000 [thread overview]
Message-ID: <50F478EB.2020108@mentor.com> (raw)
Richard,
In December I submitted a patch to replace ftest*.c in gcc.target/arm with
compile-only tests: <http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01339.html>.
There has been no response to the patch.
One reason for the replacement is that the arch_v*_multilib effective target
checks don't do what they're supposed to do and sometimes cause the simulator
and QEMU to hang, as described in PR testsuite/55780.
Please review the patch or encourage someone to fix the effective target
checks.
Janis
next reply other threads:[~2013-01-14 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 21:28 Janis Johnson [this message]
2013-01-15 15:44 ` Aldy Hernandez
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=50F478EB.2020108@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).