aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Biener <rguenther@suse.de>2022-08-30 14:37:23 +0200
committerRichard Biener <rguenther@suse.de>2022-08-30 15:38:19 +0200
commitce776225249d99b089d02424b9472811a6bbd7f5 (patch)
tree06bb02b187ddfd4f037bb4dd91829d224cdcd885
parent28b5311203fa2a691a1ed980ffa6d5ff607485b1 (diff)
downloadgcc-ce776225249d99b089d02424b9472811a6bbd7f5.zip
gcc-ce776225249d99b089d02424b9472811a6bbd7f5.tar.gz
gcc-ce776225249d99b089d02424b9472811a6bbd7f5.tar.bz2
tree-optimization/73550 - apply MAX_NUM_CHAINS consistently
The MAX_NUM_CHAINS is applied once with <= and once with < which results in the chains not limited but analyis dropped completely. That's one issue in the PR. PR tree-optimization/73550 * gimple-predicate-analysis.cc (predicate::init_from_control_deps): Do not apply MAX_NUM_CHAINS again.
-rw-r--r--gcc/gimple-predicate-analysis.cc7
1 files changed, 0 insertions, 7 deletions
diff --git a/gcc/gimple-predicate-analysis.cc b/gcc/gimple-predicate-analysis.cc
index 068196c..00c6bfc 100644
--- a/gcc/gimple-predicate-analysis.cc
+++ b/gcc/gimple-predicate-analysis.cc
@@ -1674,13 +1674,6 @@ predicate::init_from_control_deps (const vec<edge> *dep_chains,
if (num_chains == 0)
return;
- if (num_chains >= MAX_NUM_CHAINS)
- {
- if (dump_file)
- fprintf (dump_file, "MAX_NUM_CHAINS exceeded: %u\n", num_chains);
- return;
- }
-
/* Convert the control dependency chain into a set of predicates. */
m_preds.reserve (num_chains);