public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: "Martin Liška" <mliska@suse.cz>,
	"David Malcolm" <dmalcolm@redhat.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][pushed] analyzer: document new param
Date: Mon, 15 Mar 2021 14:57:02 -0600	[thread overview]
Message-ID: <73368dc8-396d-68f6-7cf0-ce87b8ad1063@gmail.com> (raw)
In-Reply-To: <b974043d-5bf0-8f7c-f9b9-cace7118152c@suse.cz>

On 3/12/21 7:02 AM, Martin Liška wrote:
> On 3/12/21 2:56 PM, David Malcolm wrote:
>> On Fri, 2021-03-12 at 09:45 +0100, Martin Liška wrote:
>>> Identified by my check that compares documentation of params
>>> with content of --help=param output.
>>>
>>> Pushed as obvious.
>>> Martin
>>
>> Thanks.
>>
>> Which check is this, BTW?  (presumably this is something I should add
>> to my patch testing workflow)
> 
> ./gcc/xgcc -Bgcc --help=param &>params.txt
> ../contrib/check-params-in-docs.py ../gcc/doc/invoke.texi params.txt

Any plans to integrate it into the testsuite?  (That way we presumably
wouldn't need to remember to run it by hand.)

Martin

> 
> Cheers,
> Martin
> 
>>
>> Dave
>>
>>> gcc/ChangeLog:
>>>
>>>          * doc/invoke.texi: Add missing param documentation.
>>> ---
>>>    gcc/doc/invoke.texi | 4 ++++
>>>    1 file changed, 4 insertions(+)
>>>
>>> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
>>> index 4a3c1e2fa0f..7a368959e5e 100644
>>> --- a/gcc/doc/invoke.texi
>>> +++ b/gcc/doc/invoke.texi
>>> @@ -14362,6 +14362,10 @@ recurse deeper.
>>>    The maximum depth of a symbolic value, before approximating
>>>    the value as unknown.
>>> +@item analyzer-max-infeasible-edges
>>> +The maximum number of infeasible edges to reject before declaring
>>> +a diagnostic as infeasible.
>>> +
>>>    @item gimple-fe-computed-hot-bb-threshold
>>>    The number of executions of a basic block which is considered hot.
>>>    The parameter is used only in GIMPLE FE.
>>
>>
> 


  reply	other threads:[~2021-03-15 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  8:45 Martin Liška
2021-03-12 13:56 ` David Malcolm
2021-03-12 14:02   ` Martin Liška
2021-03-15 20:57     ` Martin Sebor [this message]
2021-03-16  9:08       ` Martin Liška
2021-03-16 14:51         ` Martin Sebor
2021-03-16 15:09           ` testsuite: automatically checking for param documentation David Malcolm
2021-03-16 15:14             ` Martin Liška

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=73368dc8-396d-68f6-7cf0-ce87b8ad1063@gmail.com \
    --to=msebor@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).