From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Yvan Roux <yvan.roux@linaro.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: [PATCH, ARM] Fix testcases that require Thumb2 effective target.
Date: Tue, 05 May 2015 08:16:00 -0000 [thread overview]
Message-ID: <55487C5F.1030300@arm.com> (raw)
In-Reply-To: <CAD57uCfWrN8LgcfMVBmW_ssx-MJwRLzsBJt_-yfuqYo+3K-1Gg@mail.gmail.com>
On 04/05/15 10:14, Yvan Roux wrote:
> Hi,
>
> This patch fixes two ARM testcases that require target to be Thumb2
> effective. One is built for Cortex-m3, the purpose of the second one
> is to generate thumb2_addsi3_compare0_scratch insn and both are
> failing when compiled for armv5t for instance.
>
> Built and regtested, is it OK for trunk ?
Ok.
Thanks,
Kyrill
>
> Thanks,
> Yvan
>
> 2015-05-04 Yvan Roux <yvan.roux@linaro.org>
>
> * gcc.target/arm/pr65067.c: Require Thumb2 effective target.
> * gcc.target/arm/pr65924.c: Likewise.
prev parent reply other threads:[~2015-05-05 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:14 Yvan Roux
2015-05-05 8:16 ` Kyrill Tkachov [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=55487C5F.1030300@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=yvan.roux@linaro.org \
/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).