diff options
author | Tamar Christina <tamar.christina@arm.com> | 2023-12-24 19:17:13 +0000 |
---|---|---|
committer | Tamar Christina <tamar.christina@arm.com> | 2023-12-24 19:17:13 +0000 |
commit | f1dcc0fe371e3cb10d2cbe3f6c88db6f72edddda (patch) | |
tree | 52b2945778b46c2976c2db5e4e316bce13aa98db /gcc/tree-vectorizer.h | |
parent | 0994ddd86f9c3d829b06009d9e706ff72b07001a (diff) | |
download | gcc-f1dcc0fe371e3cb10d2cbe3f6c88db6f72edddda.zip gcc-f1dcc0fe371e3cb10d2cbe3f6c88db6f72edddda.tar.gz gcc-f1dcc0fe371e3cb10d2cbe3f6c88db6f72edddda.tar.bz2 |
middle-end: prevent LIM from hoising vector compares from gconds if target does not support it.
LIM notices that in some cases the condition and the results are loop
invariant and tries to move them out of the loop.
While the resulting code is operationally sound, moving the compare out of the
gcond results in generating code that no longer branches, so cbranch is no
longer applicable. As such I now add code to check during this motion to see
if the target supports flag setting vector comparison as general operation.
I have tried writing a GIMPLE testcase for this but the gimple FE seems to be
having some trouble with the vector types. It seems to fail parsing.
The early break code testsuite however has a test for this
(vect-early-break_67.c).
gcc/ChangeLog:
* tree-ssa-loop-im.cc (determine_max_movement): Import insn-codes.h
and optabs-tree.h and check for vector compare motion out of gcond.
Diffstat (limited to 'gcc/tree-vectorizer.h')
0 files changed, 0 insertions, 0 deletions