From: charles.baylis@linaro.org
To: Ramana.Radhakrishnan@arm.com, kyrylo.tkachov@arm.com,
richard.earnshaw@arm.com
Cc: rearnsha@arm.com, gcc-patches@gcc.gnu.org, michael.collison@linaro.org
Subject: [ARM, PATCH v2 0/2] PR68532: Fix VZIP/VUZP recognition for big endian
Date: Wed, 03 Feb 2016 18:59:00 -0000 [thread overview]
Message-ID: <1454525947-14690-1-git-send-email-charles.baylis@linaro.org> (raw)
From: Charles Baylis <charles.baylis@linaro.org>
This is an updated patch, which fixes the following issues:
. big endian ICE with vshuf-* tests
. style issues reported by check_GNU_style.sh
This has no regressions with -mfpu=neon, for arm-unknown-linux-gnueabihf and
armeb-unknown-linux-gnueabihf. The new test passes for both, and big endian has
new PASSes for the vshuf-* execution tests, which currently fail on trunk.
The comment about the failures due to failure to vectorize seems to have been
incorrect.
Link to previous thread:
https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00060.html
Charles Baylis (2):
[ARM] PR68532: Fix up vuzp for big endian
[ARM] PR68532 Fix up vzip recognition for big endian
gcc/config/arm/arm.c | 77 +++++++++++++++++++++------
gcc/config/arm/arm_neon.h | 72 ++++++++++++-------------
gcc/testsuite/gcc.c-torture/execute/pr68532.c | 24 +++++++++
3 files changed, 122 insertions(+), 51 deletions(-)
create mode 100644 gcc/testsuite/gcc.c-torture/execute/pr68532.c
--
1.9.1
next reply other threads:[~2016-02-03 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 18:59 charles.baylis [this message]
2016-02-03 18:59 ` [PATCH 1/2] [ARM] PR68532: Fix up vuzp " charles.baylis
2016-02-08 11:42 ` Kyrill Tkachov
2016-02-09 17:01 ` Charles Baylis
2016-02-09 17:08 ` Kyrill Tkachov
2016-02-09 18:54 ` Charles Baylis
2016-02-03 18:59 ` [PATCH 2/2] [ARM] PR68532 Fix up vzip recognition " charles.baylis
2016-02-08 11:42 ` Kyrill Tkachov
2016-02-09 17:07 ` Charles Baylis
2016-02-09 18:53 ` Charles Baylis
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=1454525947-14690-1-git-send-email-charles.baylis@linaro.org \
--to=charles.baylis@linaro.org \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=michael.collison@linaro.org \
--cc=rearnsha@arm.com \
--cc=richard.earnshaw@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).