public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5892] param: Add missing . in description. Date: Fri, 10 Dec 2021 12:31:58 +0000 (GMT) [thread overview] Message-ID: <20211210123158.1A2A83858C27@sourceware.org> (raw) https://gcc.gnu.org/g:207775085ff03b414d63fbfc6a3c734fb0f6b396 commit r12-5892-g207775085ff03b414d63fbfc6a3c734fb0f6b396 Author: Martin Liska <mliska@suse.cz> Date: Fri Dec 10 13:31:21 2021 +0100 param: Add missing . in description. Fixes: FAIL: compiler driver --help=param option(s): "^ +-.*[^:.]$" absent from output: " --param=max-inline-functions-called-once-loop-depth= Maximum loop depth of a call which is considered for inlining functions called once" FAIL: compiler driver --help=params option(s): "[^.]$" absent from output: "e" gcc/ChangeLog: * params.opt: Add missing dot. Diff: --- gcc/params.opt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/params.opt b/gcc/params.opt index f1b5757461c..80ec6546bcd 100644 --- a/gcc/params.opt +++ b/gcc/params.opt @@ -547,7 +547,7 @@ Maximum depth of search in the dominator tree for expressions to hoist. -param=max-inline-functions-called-once-loop-depth= Common Joined UInteger Var(param_inline_functions_called_once_loop_depth) Init(6) Optimization Param -Maximum loop depth of a call which is considered for inlining functions called once +Maximum loop depth of a call which is considered for inlining functions called once. -param=max-inline-functions-called-once-insns= Common Joined UInteger Var(param_inline_functions_called_once_insns) Init(4000) Optimization Param
reply other threads:[~2021-12-10 12:31 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211210123158.1A2A83858C27@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).