]> git.ipfire.org Git - thirdparty/gcc.git/commit
[Patch (preapproved)] Guard Copy Header pass on
authorjgreenhalgh <jgreenhalgh@138bc75d-0d04-0410-961f-82ee72b054a4>
Thu, 27 Jul 2017 11:42:17 +0000 (11:42 +0000)
committerjgreenhalgh <jgreenhalgh@138bc75d-0d04-0410-961f-82ee72b054a4>
Thu, 27 Jul 2017 11:42:17 +0000 (11:42 +0000)
commit1907f06ec9ef5d5f323bb7b5d790d5d6a511e35a
treeabe762c29c8a13c910c8341c09fb0ea4cdf45529
parent7f074a78e6a3100eff2087a4cba55cc807790453
[Patch (preapproved)] Guard Copy Header pass on

While answering a user question on the equivalence of
-ftree-loop-vectorize + -ftree-slp-vectorize and -ftree-vectorize I
spotted one case which broke the equivalence. pass_ch::process_loop_p
was guarded on flag_tree_vectorize, meaning you would get it for
-ftree-vectorize, but not for -ftree-loop-vectorize/-ftree-slp-vectorize.

This patch fixes that, getting rid of the only use of flag_tree_vectorize
in the code base.

gcc/

* tree-ssa-loop-ch.c (pass_ch::process_loop_p): Guard on
flag_tree_loop_vectorize rather than flag_tree_vectorize.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@250619 138bc75d-0d04-0410-961f-82ee72b054a4
gcc/ChangeLog
gcc/tree-ssa-loop-ch.c