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/95188] State explosion on bzip2-1.0.8/bzip2.c hides -Wanalyzer-unsafe-call-within-signal-handler Date: Fri, 25 Mar 2022 20:28:57 +0000 [thread overview] Message-ID: <bug-95188-4-1YzkpNNsNi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95188-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95188 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|analyzer-unsafe-call-within |State explosion on |-signal-handler shows wrong |bzip2-1.0.8/bzip2.c hides |statement for signal |-Wanalyzer-unsafe-call-with |registration event |in-signal-handler --- Comment #14 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Comment #9 noted that the original issue here (the wrong location) was fixed, but the remaining issues are to do with state explosions. I tested with today's trunk, and the state explosions still happen (and, for me mask the signal warning, unless I pass e.g. --param=analyzer-bb-explosion-factor=50 Updating subject to reflect that (rather than opening a new bug, to keep the conversation in one place)
prev parent reply other threads:[~2022-03-25 20:28 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-18 13:28 [Bug analyzer/95188] New: analyzer-unsafe-call-within-signal-handler shows wrong statement for signal registration event mark at gcc dot gnu.org 2020-09-16 23:02 ` [Bug analyzer/95188] " cvs-commit at gcc dot gnu.org 2020-09-16 23:27 ` dmalcolm at gcc dot gnu.org 2020-09-16 23:28 ` dmalcolm at gcc dot gnu.org 2020-09-29 14:09 ` mark at gcc dot gnu.org 2020-09-29 17:31 ` dmalcolm at gcc dot gnu.org 2020-09-29 18:13 ` mark at gcc dot gnu.org 2020-09-29 19:16 ` dmalcolm at gcc dot gnu.org 2020-09-29 22:33 ` cvs-commit at gcc dot gnu.org 2020-09-29 22:42 ` dmalcolm at gcc dot gnu.org 2020-09-30 22:00 ` mark at gcc dot gnu.org 2020-10-07 14:28 ` dmalcolm at gcc dot gnu.org 2020-10-07 20:05 ` mark at gcc dot gnu.org 2021-03-12 22:35 ` dmalcolm at gcc dot gnu.org 2022-03-25 20:28 ` dmalcolm at gcc dot gnu.org [this message]
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-95188-4-1YzkpNNsNi@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).