diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2021-04-06 12:44:51 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2021-04-06 12:46:22 +0200 |
| commit | bfeb36bd03c2168af263daa13370a20a96c42b5d (patch) | |
| tree | 6984b2308f55551d30d75f6c130e081436592026 /gcc/tree-vect-loop.c | |
| parent | 58cd9fc8a61de09ba181c5ed5ac7fb91ec506414 (diff) | |
| download | gcc-bfeb36bd03c2168af263daa13370a20a96c42b5d.zip gcc-bfeb36bd03c2168af263daa13370a20a96c42b5d.tar.gz gcc-bfeb36bd03c2168af263daa13370a20a96c42b5d.tar.bz2 | |
testsuite: Fix up pr96573.c on aarch64 [PR96573]
On Thu, Apr 01, 2021 at 02:16:55PM +0100, Alex Coplan via Gcc-patches wrote:
> FYI, I'm seeing the new test failing on aarch64:
>
> PASS: gcc.dg/pr96573.c (test for excess errors)
> FAIL: gcc.dg/pr96573.c scan-tree-dump optimized "__builtin_bswap"
The vectorizer in the aarch64 case manages to emit a VEC_PERM_EXPR instead
(which is just as efficient).
So, do we want to go for the following (and/or perhaps also restrict the test to
a couple of targets where it works? In my last distro build it failed only
on aarch64-linux, while armv7hl-linux-gnueabi and
{i686,x86_64,powerpc64le,s390x}-linux were fine)?
2021-04-06 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/96573
* gcc.dg/pr96573.c: Instead of __builtin_bswap accept also
VEC_PERM_EXPR with bswapping permutation.
Diffstat (limited to 'gcc/tree-vect-loop.c')
0 files changed, 0 insertions, 0 deletions