diff options
| author | Richard Sandiford <richard.sandiford@arm.com> | 2019-11-21 17:43:24 +0000 |
|---|---|---|
| committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2019-11-21 17:43:24 +0000 |
| commit | 91f161b03b649984991573c2f2605555da4a678c (patch) | |
| tree | 4035d017f68ce2f82cb189e9204ddbb89a9f0687 /gcc/tree-iterator.c | |
| parent | 934f135b967c7501be6e2e10a2c3c03c54a198d3 (diff) | |
| download | gcc-91f161b03b649984991573c2f2605555da4a678c.zip gcc-91f161b03b649984991573c2f2605555da4a678c.tar.gz gcc-91f161b03b649984991573c2f2605555da4a678c.tar.bz2 | |
Add more markup to vect-alias-check-{1,18}.c (PR 92543)
In vect-alias-check-1.c we unroll the inner loop and then vectorise
the stores at a[c + 1][b]. Since the access has no guaranteed
alignemnt, we need a realignment mechanism or support for unaligned
accesses in order to vectorise.
In vect-alias-check-18.c we use a reverse access and so need
permute support in order to vectorise.
I'm not really sure when this part of the testsuite prefers
{ xfail { ! foo } } and when it prefers { target foo }. xfail
seems like the most common choice for the alignment restriction,
whereas vect_int and vect_perm are mostly dg-require-effective-target
style features, so I went with that combination.
2019-11-21 Richard Sandiford <richard.sandiford@arm.com>
gcc/testsuite/
PR testsuite/92543
* gcc.dg/vect/vect-alias-check-1.c: XFAIL the alias check message
if there is no realignment support and no support for unaligned
accesses.
* gcc.dg/vect/vect-alias-check-18.c: Restrict the test for the
alias message to targets that have permute support.
From-SVN: r278591
Diffstat (limited to 'gcc/tree-iterator.c')
0 files changed, 0 insertions, 0 deletions