From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id CC5873858D37; Thu,  2 Mar 2023 21:52:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC5873858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677793929;
	bh=2dwavKWuwKWdW0D4Mb1ZusvPWmJstM6YbRqA6M9IQVI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xvfRTgsQPl2pZAMYbmzqx+tjHo/fdZi9rrYnHQeDXRQv0VLjsu5V9qUzz90bBP6hO
	 Ck62+Gx4dtrJIoohq0ZlkIKrgCezzaea4I7qldNtkKanlFfnyyAAWAkeYcgGohWaU1
	 haUwVzHHXa/3RmQurVySQp1q6JAz8qXULqNJredI=
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/108968] fanalyzer false positive with the
 uninitalised-ness of the stack pointer
Date: Thu, 02 Mar 2023 21:52:09 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108968-4-8OnWTVXcMF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108968-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108968

--- Comment #18 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Looks like it doesn't even need the asm stmt at line 32 to consider that it
could take the false-then-true path.=