public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-2678] Document new analyzer parameters Date: Thu, 20 Jul 2023 14:46:00 +0000 (GMT) [thread overview] Message-ID: <20230720144600.5DB54385AFB3@sourceware.org> (raw) https://gcc.gnu.org/g:c0c5a57bff5cf2b6f3d6c55e70c0dc7d4e1fe1aa commit r14-2678-gc0c5a57bff5cf2b6f3d6c55e70c0dc7d4e1fe1aa Author: Martin Jambor <mjambor@suse.cz> Date: Thu Jul 20 16:43:36 2023 +0200 Document new analyzer parameters This patch documents the analyzer parameters introduced in r14-2029-g0e466e978c7286 also in gcc/doc/invoke.texi. 2023-07-20 Martin Jambor <mjambor@suse.cz> * doc/invoke.texi (analyzer-text-art-string-ellipsis-threshold): New. (analyzer-text-art-ideal-canvas-width): Likewise. (analyzer-text-art-string-ellipsis-head-len): Likewise. (analyzer-text-art-string-ellipsis-tail-len): Likewise. Diff: --- gcc/doc/invoke.texi | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index d3c821e208a..5628c08214d 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -16324,6 +16324,18 @@ The parameter is used only in GIMPLE FE. The maximum number of 'after supernode' exploded nodes within the analyzer per supernode, before terminating analysis. +@item analyzer-text-art-string-ellipsis-threshold +The number of bytes at which to ellipsize string literals in analyzer text art diagrams. + +@item analyzer-text-art-ideal-canvas-width +The ideal width in characters of text art diagrams generated by the analyzer. + +@item analyzer-text-art-string-ellipsis-head-len +The number of literal bytes to show at the head of a string literal in text art when ellipsizing it. + +@item analyzer-text-art-string-ellipsis-tail-len +The number of literal bytes to show at the tail of a string literal in text art when ellipsizing it. + @item ranger-logical-depth Maximum depth of logical expression evaluation ranger will look through when evaluating outgoing edge ranges.
reply other threads:[~2023-07-20 14:46 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=20230720144600.5DB54385AFB3@sourceware.org \ --to=jamborm@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).