diff options
| author | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2020-07-22 09:27:49 +0200 |
|---|---|---|
| committer | Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> | 2020-07-29 10:44:12 +0200 |
| commit | f1660ceb0d3b0076555058087307f88b80619a6f (patch) | |
| tree | 2618f154d4848882280c06f9a8c09dfd87cc3a66 /gcc | |
| parent | 269322ece17202632bc354e9c510e4a5bd6ad84b (diff) | |
| download | gcc-f1660ceb0d3b0076555058087307f88b80619a6f.zip gcc-f1660ceb0d3b0076555058087307f88b80619a6f.tar.gz gcc-f1660ceb0d3b0076555058087307f88b80619a6f.tar.bz2 | |
vect: Fix infinite loop while determining peeling amount
This is a follow up to commit 5c9669a0e6c respectively discussion
https://gcc.gnu.org/pipermail/gcc-patches/2020-June/549132.html
In case a type has a lower alignment than its size, ensure that we
advance. For example, on s390x we have for a long double an alignment
constraint of 8 bytes whereas the size is 16 bytes. Increasing the loop
variable only by TARGET_ALIGN / DR_SIZE which equals zero in case of a
long double results in an infinite loop. This is fixed by ensuring that
we advance at least by one.
gcc/ChangeLog:
* tree-vect-data-refs.c (vect_enhance_data_refs_alignment):
Ensure that loop variable npeel_tmp advances in each iteration.
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/tree-vect-data-refs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/tree-vect-data-refs.c b/gcc/tree-vect-data-refs.c index e35a215..a78ae61 100644 --- a/gcc/tree-vect-data-refs.c +++ b/gcc/tree-vect-data-refs.c @@ -1779,7 +1779,7 @@ vect_enhance_data_refs_alignment (loop_vec_info loop_vinfo) { vect_peeling_hash_insert (&peeling_htab, loop_vinfo, dr_info, npeel_tmp); - npeel_tmp += target_align / dr_size; + npeel_tmp += MAX (1, target_align / dr_size); } one_misalignment_known = true; |