public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "felix-gcc at fefe dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/95000] -fanalyzer confused by switch Date: Fri, 08 May 2020 09:57:56 +0000 [thread overview] Message-ID: <bug-95000-4-bQVVHVwV5U@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95000-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000 --- Comment #2 from felix-gcc at fefe dot de --- The false positive also happens if you fix that. In fact, my original (much longer) code does not try to write to read-only memory. I put that in my test case in the hope that somebody would mention it, so I can point out that gcc -fanalyzer could warn about it, but doesn't. So thank you for falling for my trap. :-)
next prev parent reply other threads:[~2020-05-08 9:57 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 8:59 [Bug analyzer/95000] New: " felix-gcc at fefe dot de 2020-05-08 9:49 ` [Bug analyzer/95000] " jakub at gcc dot gnu.org 2020-05-08 9:57 ` felix-gcc at fefe dot de [this message] 2020-05-08 14:11 ` dmalcolm at gcc dot gnu.org 2020-05-08 14:25 ` [Bug analyzer/95000] -fanalyzer confused by switch on non-int type dmalcolm at gcc dot gnu.org 2021-02-11 15:12 ` dimhen at gmail dot com 2022-03-15 18:45 ` dmalcolm at gcc dot gnu.org 2022-03-15 21:57 ` cvs-commit 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-95000-4-bQVVHVwV5U@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).