[gcc r13-2279] tree-optimization/73550 - apply MAX_NUM_CHAINS consistently

[Richard Biener <rguenth@gcc.gnu.org>]

https://gcc.gnu.org/g:ce776225249d99b089d02424b9472811a6bbd7f5

commit r13-2279-gce776225249d99b089d02424b9472811a6bbd7f5
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Aug 30 14:37:23 2022 +0200

    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.

Diff:
---
 gcc/gimple-predicate-analysis.cc | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/gcc/gimple-predicate-analysis.cc b/gcc/gimple-predicate-analysis.cc
index 068196cb157..00c6bfc50a3 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);