From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 2/2] Remove --param max-fsm-thread-length
Date: Tue, 9 Aug 2022 08:23:35 +0000 (UTC) [thread overview]
Message-ID: <20220809082335.MCFCO-xgGfQhjNrkGBrC9frSvhsFKy0JpqRBnObBzmY@z> (raw)
This removes max-fsm-thread-length which is obsoleted by
max-jump-thread-paths.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
* doc/invoke.texi (max-fsm-thread-length): Remove.
* params.opt (max-fsm-thread-length): Likewise.
* tree-ssa-threadbackward.cc
(back_threader_profitability::profitable_path_p): Do not
check max-fsm-thread-length.
---
gcc/doc/invoke.texi | 3 ---
gcc/params.opt | 4 ----
gcc/tree-ssa-threadbackward.cc | 9 ---------
3 files changed, 16 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index f01696696bf..58e422041e4 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -15262,9 +15262,6 @@ Emit instrumentation calls to __tsan_func_entry() and __tsan_func_exit().
Maximum number of instructions to copy when duplicating blocks on a
finite state automaton jump thread path.
-@item max-fsm-thread-length
-Maximum number of basic blocks on a jump thread path.
-
@item threader-debug
threader-debug=[none|all] Enables verbose dumping of the threader solver.
diff --git a/gcc/params.opt b/gcc/params.opt
index 132987343c6..201b5c9f56f 100644
--- a/gcc/params.opt
+++ b/gcc/params.opt
@@ -498,10 +498,6 @@ The maximum number of nested indirect inlining performed by early inliner.
Common Joined UInteger Var(param_max_fields_for_field_sensitive) Param
Maximum number of fields in a structure before pointer analysis treats the structure as a single variable.
--param=max-fsm-thread-length=
-Common Joined UInteger Var(param_max_fsm_thread_length) Init(10) IntegerRange(1, 999999) Param Optimization
-Maximum number of basic blocks on a jump thread path.
-
-param=max-fsm-thread-path-insns=
Common Joined UInteger Var(param_max_fsm_thread_path_insns) Init(100) IntegerRange(1, 999999) Param Optimization
Maximum number of instructions to copy when duplicating blocks on a finite state automaton jump thread path.
diff --git a/gcc/tree-ssa-threadbackward.cc b/gcc/tree-ssa-threadbackward.cc
index bb1ef514abf..741c923e1a6 100644
--- a/gcc/tree-ssa-threadbackward.cc
+++ b/gcc/tree-ssa-threadbackward.cc
@@ -568,15 +568,6 @@ back_threader_profitability::profitable_path_p (const vec<basic_block> &m_path,
if (m_path.length () <= 1)
return false;
- if (m_path.length () > (unsigned) param_max_fsm_thread_length)
- {
- if (dump_file && (dump_flags & TDF_DETAILS))
- fprintf (dump_file, " FAIL: Jump-thread path not considered: "
- "the number of basic blocks on the path "
- "exceeds PARAM_MAX_FSM_THREAD_LENGTH.\n");
- return false;
- }
-
int n_insns = 0;
gimple_stmt_iterator gsi;
loop_p loop = m_path[0]->loop_father;
--
2.35.3
next reply other threads:[~2022-08-09 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 8:23 Richard Biener [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-09 8:23 Richard Biener
2022-08-09 8:23 Richard Biener
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220809082335.MCFCO-xgGfQhjNrkGBrC9frSvhsFKy0JpqRBnObBzmY@z \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).