From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 60A473858D39; Mon, 25 Mar 2024 18:40:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 60A473858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1711392033; bh=HBPeR5/u9kz2dLU3+oFDxmKi1NmubeBAx/LMWXCqhjY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rJgmNR1U8bRkMPRMCffOYD2W8+jzI3POLnfci9qY9QgVWWoRO1daOJ5/teMSfN2rR vdgDmPN+G/FnYOQLaVf0DF6zGcovK/e01g7KuANrqqn/b+NQzUbhSsekmP01qNpVKd lW7hlxwD8bp1WgDFblEge8hEWxAq2vsenSjCsMT8= From: "pinskia at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113314 --- Comment #3 from Andrew Pinski --- Note a volatile memory location change even without this being multi-thread= ed; an async signal (USR1..USR4, or ALRM, etc.) could come in and change the va= lue. Or the memory could be shared memory between 2 different processes; though I suspect in that case you want to use atomics.=