From: Aldy Hernandez <aldyh@redhat.com>
To: <janisjo@codesourcery.com>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <rearnsha@arm.com>
Subject: Re: PING: replace gcc.target/arm/ftest-*.c with compile-only tests
Date: Tue, 15 Jan 2013 15:44:00 -0000 [thread overview]
Message-ID: <87txqijvs9.fsf@houston.quesejoda.com> (raw)
In-Reply-To: <50F478EB.2020108@mentor.com> (Janis Johnson's message of "Mon, 14 Jan 2013 13:30:19 -0800")
Janis Johnson <janis_johnson@mentor.com> writes:
> 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.
Hmmm, I wonder if PR54139 is a duplicate of the aforementioned PR:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54139
Janis, do you think this is the same problem?
prev parent reply other threads:[~2013-01-15 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 21:28 Janis Johnson
2013-01-15 15:44 ` Aldy Hernandez [this message]
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=87txqijvs9.fsf@houston.quesejoda.com \
--to=aldyh@redhat.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).