mirror of
https://github.com/gcc-mirror/gcc.git
synced 2026-05-06 14:59:39 +02:00
fdf84733a3
In this case, early phiopt would get rid of the user provided predicator for hot/cold as it would remove the basic blocks. The easiest and best option is for early phi-opt don't do phi-opt if the middle basic-block(s) have either a hot or cold predict statement. Then after inlining, jump threading will most likely happen and that will keep around the predictor. Note this only needs to be done for match_simplify_replacement and not the other phi-opt functions because currently only match_simplify_replacement is able to skip middle bb with predicator statements in it. This allows for MIN/MAX/ABS/NEG still even with the predicators there as those will less likely be jump threaded later on. The main thing that is rejected is ssa names that are alone where one of the comparisons operands is that one or if we produce a comparison from the phiopt. Changes since v1: * v2: Only reject if the result was the comparison. Bootstrapped and tested on x86_64-linux-gnu. PR tree-optimization/117935 gcc/ChangeLog: * tree-ssa-phiopt.cc (contains_hot_cold_predict): New function. (match_simplify_replacement): Return early if early_p and one of the middle bb(s) have a hot/cold predict statement. gcc/testsuite/ChangeLog: * gcc.dg/predict-24.c: New test. * gcc.dg/predict-25.c: New test. Signed-off-by: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.