diff options
| author | Tamar Christina <tamar.christina@arm.com> | 2023-10-20 14:58:39 +0100 |
|---|---|---|
| committer | Tamar Christina <tamar.christina@arm.com> | 2023-10-20 15:00:37 +0100 |
| commit | eb15fad3190a8b33e3e451b964ff1ecf08bbb113 (patch) | |
| tree | ec0b7c1c706dfd58dbc44798d584f8976f70c0fe /gcc/cp/constexpr.cc | |
| parent | a1fc2cc0a8a8b97dbc3dc6715fd4f384d9204845 (diff) | |
| download | gcc-eb15fad3190a8b33e3e451b964ff1ecf08bbb113.zip gcc-eb15fad3190a8b33e3e451b964ff1ecf08bbb113.tar.gz gcc-eb15fad3190a8b33e3e451b964ff1ecf08bbb113.tar.bz2 | |
middle-end: don't pass loop_vinfo to vect_set_loop_condition during prolog peeling
During the refactoring I had passed loop_vinfo on to vect_set_loop_condition
during prolog peeling. This parameter is unused in most cases except for in
vect_set_loop_condition_partial_vectors where it's behaviour depends on whether
loop_vinfo is NULL or not. Apparently this code expect it to be NULL and it
reads the structures from a different location.
This fixes the failing testcase which was not using the lens values determined
earlier in vectorizable_store because it was looking it up in the given
loop_vinfo instead.
gcc/ChangeLog:
PR tree-optimization/111866
* tree-vect-loop-manip.cc (vect_do_peeling): Pass null as vinfo to
vect_set_loop_condition during prolog peeling.
Diffstat (limited to 'gcc/cp/constexpr.cc')
0 files changed, 0 insertions, 0 deletions