diff options
| author | Andrew Stubbs <ams@codesourcery.com> | 2022-08-05 13:28:50 +0100 |
|---|---|---|
| committer | Andrew Stubbs <ams@codesourcery.com> | 2022-08-30 15:50:17 +0100 |
| commit | f134a25ee8c29646f35f7e466109f6a7f5b9e824 (patch) | |
| tree | 3cbbf9b4be50af4c2fcb724e0d2a879b210c4680 /gcc/value-range.cc | |
| parent | 1025025b612d632920fe710bb58d36e4d43f3220 (diff) | |
| download | gcc-f134a25ee8c29646f35f7e466109f6a7f5b9e824.zip gcc-f134a25ee8c29646f35f7e466109f6a7f5b9e824.tar.gz gcc-f134a25ee8c29646f35f7e466109f6a7f5b9e824.tar.bz2 | |
omp-simd-clone: Allow fixed-lane vectors
The vecsize_int/vecsize_float has an assumption that all arguments will use
the same bitsize, and vary the number of lanes according to the element size,
but this is inappropriate on targets where the number of lanes is fixed and
the bitsize varies (i.e. amdgcn).
With this change the vecsize can be left zero and the vectorization factor will
be the same for all types.
gcc/ChangeLog:
* doc/tm.texi: Regenerate.
* omp-simd-clone.cc (simd_clone_adjust_return_type): Allow zero
vecsize.
(simd_clone_adjust_argument_types): Likewise.
* target.def (compute_vecsize_and_simdlen): Document the new
vecsize_int and vecsize_float semantics.
Diffstat (limited to 'gcc/value-range.cc')
0 files changed, 0 insertions, 0 deletions