diff options
author | Richard Sandiford <richard.sandiford@arm.com> | 2021-07-13 10:17:34 +0100 |
---|---|---|
committer | Richard Sandiford <richard.sandiford@arm.com> | 2021-07-13 10:17:34 +0100 |
commit | 0ae469e8c0ccb93a26bb1e60db6418d6bcced15e (patch) | |
tree | ed6284907698990f773d1bc984bbed5e8f277677 /gcc/tree-vect-loop.c | |
parent | dddb6ffdc5c25264dd75ad82dad8e48a0718d2d9 (diff) | |
download | gcc-0ae469e8c0ccb93a26bb1e60db6418d6bcced15e.zip gcc-0ae469e8c0ccb93a26bb1e60db6418d6bcced15e.tar.gz gcc-0ae469e8c0ccb93a26bb1e60db6418d6bcced15e.tar.bz2 |
ifcvt: Improve tests for predicated operations
-msve-vector-bits=128 causes the AArch64 port to list 128-bit Advanced
SIMD as the first-choice mode for vectorisation, with SVE being used for
things that Advanced SIMD can't handle as easily. However, ifcvt would
not then try to use SVE's predicated FP arithmetic, leading to tests
like TSVC ControlFlow-flt failing to vectorise.
The mask load/store code did try other vector modes, but could also be
improved to make sure that SVEness sticks when computing derived modes.
(Unlike mode_for_vector, related_vector_mode always returns a vector
mode, so there's no need to check VECTOR_MODE_P as well.)
gcc/
* internal-fn.c (vectorized_internal_fn_supported_p): Handle
vector types first. For scalar types, consider both the preferred
vector mode and the alternative vector modes.
* optabs-query.c (can_vec_mask_load_store_p): Use the same
structure as above, in particular using related_vector_mode
for modes provided by autovectorize_vector_modes.
gcc/testsuite/
* gcc.target/aarch64/sve/cond_arith_6.c: New test.
Diffstat (limited to 'gcc/tree-vect-loop.c')
0 files changed, 0 insertions, 0 deletions