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 r13-3960] Partially revert 12c583a2a3da798e82737c2d0e11fd686636cfeb Date: Mon, 14 Nov 2022 08:36:29 +0000 (GMT) [thread overview] Message-ID: <20221114083634.C009B385841D@sourceware.org> (raw) https://gcc.gnu.org/g:d33b561eb6842a269125a5f14ca0192e783b96cf commit r13-3960-gd33b561eb6842a269125a5f14ca0192e783b96cf Author: Martin Liska <mliska@suse.cz> Date: Sun Nov 13 21:52:28 2022 +0100 Partially revert 12c583a2a3da798e82737c2d0e11fd686636cfeb gcc/ChangeLog: * doc/gcc/gcc-command-options/options-that-control-static-analysis.rst: Revert. * doc/gcc/gcc-command-options/options-to-request-or-suppress-warnings.rst: Revert. Diff: --- .../options-that-control-static-analysis.rst | 28 ---------------------- .../options-to-request-or-suppress-warnings.rst | 4 ---- 2 files changed, 32 deletions(-) diff --git a/gcc/doc/gcc/gcc-command-options/options-that-control-static-analysis.rst b/gcc/doc/gcc/gcc-command-options/options-that-control-static-analysis.rst index 32a626c16a9..09bf049036f 100644 --- a/gcc/doc/gcc/gcc-command-options/options-that-control-static-analysis.rst +++ b/gcc/doc/gcc/gcc-command-options/options-that-control-static-analysis.rst @@ -32,7 +32,6 @@ Options That Control Static Analysis :option:`-Wanalyzer-file-leak` |gol| :option:`-Wanalyzer-free-of-non-heap` |gol| :option:`-Wanalyzer-imprecise-fp-arithmetic` |gol| - :option:`-Wanalyzer-infinite-recursion` |gol| :option:`-Wanalyzer-jump-through-null` |gol| :option:`-Wanalyzer-malloc-leak` |gol| :option:`-Wanalyzer-mismatching-deallocation` |gol| @@ -309,33 +308,6 @@ Options That Control Static Analysis Default setting; overrides :option:`-Wno-analyzer-imprecise-fp-arithmetic`. -.. option:: -Wno-analyzer-infinite-recursion - - This warning requires :option:`-fanalyzer`, which enables it; use - :option:`-Wno-analyzer-infinite-recursion` to disable it. - - This diagnostics warns for paths through the code which appear to - lead to infinite recursion. - - Specifically, when the analyzer "sees" a recursive call, it will compare - the state of memory at the entry to the new frame with that at the entry - to the previous frame of that function on the stack. The warning is - issued if nothing in memory appears to be changing; any changes observed - to parameters or globals are assumed to lead to termination of the - recursion and thus suppress the warning. - - This diagnostic is likely to miss cases of infinite recursion that - are convered to iteration by the optimizer before the analyzer "sees" - them. Hence optimization should be disabled when attempting to trigger - this diagnostic. - - Compare with :option:`-Winfinite-recursion`, which provides a similar - diagnostic, but is implemented in a different way. - -.. option:: -Wanalyzer-infinite-recursion - - Default setting; overrides :option:`-Wno-analyzer-infinite-recursion`. - .. option:: -Wno-analyzer-jump-through-null This warning requires :option:`-fanalyzer`, which enables it; use diff --git a/gcc/doc/gcc/gcc-command-options/options-to-request-or-suppress-warnings.rst b/gcc/doc/gcc/gcc-command-options/options-to-request-or-suppress-warnings.rst index b57f4784780..a4a288859c6 100644 --- a/gcc/doc/gcc/gcc-command-options/options-to-request-or-suppress-warnings.rst +++ b/gcc/doc/gcc/gcc-command-options/options-to-request-or-suppress-warnings.rst @@ -804,10 +804,6 @@ warnings, in some cases it may also cause false positives. recursion in calls between two or more functions. :option:`-Winfinite-recursion` is included in :option:`-Wall`. - Compare with :option:`-Wanalyzer-infinite-recursion` which provides a - similar diagnostic, but is implemented in a different way (as part of - :option:`-fanalyzer`). - .. option:: -Wno-infinite-recursion Default setting; overrides :option:`-Winfinite-recursion`.
reply other threads:[~2022-11-14 8:36 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=20221114083634.C009B385841D@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).