aboutsummaryrefslogtreecommitdiff
path: root/gcc/gimple-range-infer.cc
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2023-02-10 11:07:30 +0100
committerRichard Biener <rguenther@suse.de>2023-02-10 12:21:41 +0100
commitdc87e1391c55c666c7ff39d4f0dea87666f25468 (patch)
tree38e33d8ef90915dfaf3e9ec58344e3dd0c395a3d /gcc/gimple-range-infer.cc
parent2a37a4a3cbfaecb6c7666109353bb4d5c97b0702 (diff)
downloadgcc-dc87e1391c55c666c7ff39d4f0dea87666f25468.zip
gcc-dc87e1391c55c666c7ff39d4f0dea87666f25468.tar.gz
gcc-dc87e1391c55c666c7ff39d4f0dea87666f25468.tar.bz2
tree-optimization/108724 - vectorized code getting piecewise expanded
This fixes an oversight to when removing the hard limits on using generic vectors for the vectorizer to enable both SLP and BB vectorization to use those. The vectorizer relies on vector lowering to expand plus, minus and negate to bit operations but vector lowering has a hard limit on the minimum number of elements per work item. Vectorizer costs for the testcase at hand work out to vectorize a loop with just two work items per vector and that causes element wise expansion and spilling. The fix for now is to re-instantiate the hard limit, matching what vector lowering does. For the future the way to go is to emit the lowered sequence directly from the vectorizer instead. PR tree-optimization/108724 * tree-vect-stmts.cc (vectorizable_operation): Avoid using word_mode vectors when vector lowering will decompose them to elementwise operations. * gcc.target/i386/pr108724.c: New testcase.
Diffstat (limited to 'gcc/gimple-range-infer.cc')
0 files changed, 0 insertions, 0 deletions