From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Renlin Li <renlin.li@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Alan Lawrence <Alan.Lawrence@arm.com>
Subject: Re: [PATCH][AARCH64]Use shl for vec_shr_<mode> rtx pattern.
Date: Thu, 30 Apr 2015 15:23:00 -0000 [thread overview]
Message-ID: <CAFqB+PzrKP=EbQoo6CHBs5EPkhLH3gxCwq4Cp7XGmWtwu7PJ3Q@mail.gmail.com> (raw)
In-Reply-To: <5542184D.8010500@arm.com>
On 30 April 2015 at 12:55, Renlin Li <renlin.li@arm.com> wrote:
> 2015-04-30 Renlin Li <renlin.li@arm.com>
>
> * config/aarch64/aarch64-simd.md (vec_shr): Defined as an unspec.
> * config/aarch64/iterators.md (unspec): Add UNSPEC_VEC_SHR.
>
> gcc/testsuite/ChangeLog:
>
> 2015-04-30 Renlin Li <renlin.li@arm.com>
>
> * gcc.target/aarch64/vect-reduc-or_1.c: New.
+ __builtin_printf("Failed %d\n", sum);
+ abort();
Space before (
Otherwise OK /Marcus
next prev parent reply other threads:[~2015-04-30 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 16:01 Renlin Li
2015-04-29 12:10 ` Marcus Shawcroft
2015-04-30 11:58 ` Renlin Li
2015-04-30 15:23 ` Marcus Shawcroft [this message]
2015-06-02 9:30 ` Renlin Li
2015-06-02 9:48 ` Marcus Shawcroft
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='CAFqB+PzrKP=EbQoo6CHBs5EPkhLH3gxCwq4Cp7XGmWtwu7PJ3Q@mail.gmail.com' \
--to=marcus.shawcroft@gmail.com \
--cc=Alan.Lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=renlin.li@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).