diff options
| author | Richard Sandiford <richard.sandiford@arm.com> | 2019-07-10 18:41:44 +0000 |
|---|---|---|
| committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2019-07-10 18:41:44 +0000 |
| commit | 8ba8ebffc4621552febf47eea470c260488418b5 (patch) | |
| tree | 5fe02dc25c3ed66bc8fbe055e569aaae21a0fede /gcc/fold-const.c | |
| parent | 4b8d9b23371d3ee0f7a9c1d99e80745400542930 (diff) | |
| download | gcc-8ba8ebffc4621552febf47eea470c260488418b5.zip gcc-8ba8ebffc4621552febf47eea470c260488418b5.tar.gz gcc-8ba8ebffc4621552febf47eea470c260488418b5.tar.bz2 | |
[arm] Fix BE index for single-var vector initialisers (PR91060)
If a vector constructor has a single nonconstant element,
neon_expand_vector_init loads the constant lanes and then inserts the
nonconstant value. The problem was that it was doing the insertion
using the arm_neon.h neon_vset_lane<mode> patterns, which use
architectural lane numbering rather than GCC lane numbering.
2019-07-10 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR target/91060
* config/arm/iterators.md (V2DI_ONLY): New mode iterator.
* config/arm/neon.md (vec_set<mode>_internal): Add a '@' prefix.
(vec_setv2di_internal): Reexpress as...
(@vec_set<V2DI_ONLY:mode>_internal): ...this.
* config/arm/arm.c (neon_expand_vector_init): Use gen_vec_set_internal
rather than gen_neon_vset_lane<mode>.
From-SVN: r273365
Diffstat (limited to 'gcc/fold-const.c')
0 files changed, 0 insertions, 0 deletions