diff options
| author | Richard Sandiford <richard.sandiford@linaro.org> | 2018-02-08 15:17:20 +0000 |
|---|---|---|
| committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2018-02-08 15:17:20 +0000 |
| commit | b5ec4de777870e2d4ff2a5de604eafd1bf0e50df (patch) | |
| tree | 7d1c4f72e10b0597eae8549d8a317239cd7adf16 /libgo | |
| parent | fff2290073cc2d57dcade125227b74cd27c48066 (diff) | |
| download | gcc-b5ec4de777870e2d4ff2a5de604eafd1bf0e50df.zip gcc-b5ec4de777870e2d4ff2a5de604eafd1bf0e50df.tar.gz gcc-b5ec4de777870e2d4ff2a5de604eafd1bf0e50df.tar.bz2 | |
Another fix for single-element permutes (PR 84265)
PR83753 was about a case in which we ended up trying to "vectorise"
a group of loads ore stores using single-element vectors. The problem
was that we were classifying the load or store as VMAT_CONTIGUOUS_PERMUTE
rather than VMAT_CONTIGUOUS, even though it doesn't make sense to permute
a single-element vector.
In that PR it was enough to change get_group_load_store_type,
because vectorisation ended up being unprofitable and so we didn't
take things further. But when vectorisation is profitable, the same
fix is needed in vectorizable_load and vectorizable_store.
2018-02-08 Richard Sandiford <richard.sandiford@linaro.org>
gcc/
PR tree-optimization/84265
* tree-vect-stmts.c (vectorizable_store): Don't treat
VMAT_CONTIGUOUS accesses as grouped.
(vectorizable_load): Likewise.
gcc/testsuite/
PR tree-optimization/84265
* gcc.dg/vect/pr84265.c: New test.
From-SVN: r257492
Diffstat (limited to 'libgo')
0 files changed, 0 insertions, 0 deletions