public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/113314] [14 Regression] -Wanalyzer-infinite-loop false positive seen on haproxy's fd.c Date: Mon, 25 Mar 2024 18:40:32 +0000 [thread overview] Message-ID: <bug-113314-4-n1wSMfN30X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113314 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note a volatile memory location change even without this being multi-threaded; an async signal (USR1..USR4, or ALRM, etc.) could come in and change the value. Or the memory could be shared memory between 2 different processes; though I suspect in that case you want to use atomics.
next prev parent reply other threads:[~2024-03-25 18:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 20:42 [Bug analyzer/113314] New: " dmalcolm at gcc dot gnu.org 2024-01-10 22:01 ` [Bug analyzer/113314] " dmalcolm at gcc dot gnu.org 2024-02-16 13:54 ` [Bug analyzer/113314] [14 Regression] " dmalcolm at gcc dot gnu.org 2024-03-04 13:05 ` rguenth at gcc dot gnu.org 2024-03-07 20:51 ` law at gcc dot gnu.org 2024-03-25 16:12 ` dmalcolm at gcc dot gnu.org 2024-03-25 18:40 ` pinskia at gcc dot gnu.org [this message] 2024-05-07 7:43 ` [Bug analyzer/113314] [14/15 " rguenth 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-113314-4-n1wSMfN30X@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).