Remove callgraph cycle threshold now that it is no longer used
Bug: 143685705
Change-Id: Id9bdfbcfdb5d5139341a5fa662cf6bd4d41d0aa6
diff --git a/src/main/java/com/android/tools/r8/utils/InternalOptions.java b/src/main/java/com/android/tools/r8/utils/InternalOptions.java
index 828e8d2..129189b 100644
--- a/src/main/java/com/android/tools/r8/utils/InternalOptions.java
+++ b/src/main/java/com/android/tools/r8/utils/InternalOptions.java
@@ -218,11 +218,6 @@
public boolean encodeChecksums = false;
public BiPredicate<String, Long> dexClassChecksumFilter = (name, checksum) -> true;
- // This defines the max depth threshold for the cycle eliminator. If the length of a call chain
- // exceeds the threshold, we treat it as if we have found a cycle. This ensures that we won't run
- // into stack overflows when the call graph contains large call chains. This should have a
- // negligible impact on code size as long as the threshold is large enough.
- public int callGraphCycleEliminatorMaxDepthThreshold = 256;
public int callGraphLikelySpuriousCallEdgeThreshold = 50;
// TODO(b/141719453): The inlining limit at least should be consistent with normal inlining.
