diff options
author | Alexandre Oliva <oliva@adacore.com> | 2024-05-24 08:32:04 -0300 |
---|---|---|
committer | Alexandre Oliva <oliva@gnu.org> | 2024-05-24 08:32:04 -0300 |
commit | 7acd5d71547f74a2af35bab1b17a518197d25d23 (patch) | |
tree | e0fe54174f10c6a1727d8d819e403d17dd330783 /gcc/cp/module.cc | |
parent | 85e2ce10f76aee93e43aab6558cf8e39cec911e4 (diff) | |
download | gcc-7acd5d71547f74a2af35bab1b17a518197d25d23.zip gcc-7acd5d71547f74a2af35bab1b17a518197d25d23.tar.gz gcc-7acd5d71547f74a2af35bab1b17a518197d25d23.tar.bz2 |
testsuite: adjust iteration count for ppc costmodel 76b
For some hardware which doesn't support unaligned vector memory access,
test case costmodel-vect-76b.c expects to see cost modeling would make
the decision that it's not profitable for peeling, according to the
commit history, test case comments and the way to check.
For now, the existing loop bound 14 works well for Power7, but it does
not for some targets on which the cost of operation vec_perm can be
different from Power7, such as: Power6, it's 3 vs. 1. This difference
further causes the difference (10 vs. 12) on the minimum iteration for
profitability and cause the failure. To keep the original test point,
this patch is to tweak the loop bound to ensure it's not profitable
to be vectorized for !vect_no_align with peeling.
Co-Authored-By: Kewen Lin <linkw@linux.ibm.com>
for gcc/testsuite/ChangeLog
* gcc.dg/vect/costmodel/ppc/costmodel-vect-76b.c (N): Tweak.
Diffstat (limited to 'gcc/cp/module.cc')
0 files changed, 0 insertions, 0 deletions