public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/106147] RFE: -fanalyzer could complain about some cases of infinite loops and infinite recursion Date: Thu, 10 Nov 2022 20:38:41 +0000 [thread overview] Message-ID: <bug-106147-4-tV5BPExxe5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106147-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106147 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=88232 --- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> --- -Winfinite-recursion was implemented as PR 88232, which complains if every path through a function calls itself. I have a mostly-finished implementation of a new -Wanalyzer-infinite-recursion which complains if there is an interprocedural path through the code in which a function is called recursively where there's no significant change to the content of memory between calls, so it detects cases like: void test_guarded (int flag) { if (flag) test_guarded (flag); }
next prev parent reply other threads:[~2022-11-10 20:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-30 12:46 [Bug analyzer/106147] New: " dmalcolm at gcc dot gnu.org 2022-06-30 12:57 ` [Bug analyzer/106147] " dmalcolm at gcc dot gnu.org 2022-07-29 22:20 ` dmalcolm at gcc dot gnu.org 2022-08-10 13:48 ` dmalcolm at gcc dot gnu.org 2022-11-10 20:38 ` dmalcolm at gcc dot gnu.org [this message] 2022-11-11 21:04 ` cvs-commit at gcc dot gnu.org 2022-11-11 21:24 ` dmalcolm at gcc dot gnu.org 2023-11-18 0:59 ` cvs-commit at gcc dot gnu.org 2024-01-12 19:14 ` dmalcolm at gcc dot gnu.org 2024-01-20 17:20 ` pinskia at gcc dot gnu.org
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=bug-106147-4-tV5BPExxe5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).