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 465A93858D33; Tue, 28 Feb 2023 15:41:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 465A93858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677598912;
	bh=UvhteLVKOxkyA3qEsuy5DMWsfjuA5zcW2El4NuRjopk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=k3m9eVVfgi+eY0iIwJ9p2NMBj0/LZ5j0FXOq1bhrCLFqcY4NOtoIzrBjCr/nHkC9s
	 sVZphljd995ClXb/bmOi9zFeQABuImJ8D57oNQneT5pRXPOi9dqLDqlJFyyOXy9z9l
	 KiGolkZRsHEAzbSldUnLcqkEqJbItjuh/DRUPicU=
From: "andrew.cooper3 at citrix dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108968] fanalyzer false positive with the uninitalised-ness
 of the stack pointer
Date: Tue, 28 Feb 2023 15:41:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew.cooper3 at citrix dot com
X-Bugzilla-Status: UNCONFIRMED
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: component
Message-ID: <bug-108968-4-nydGAueGtI@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

Andrew Cooper <andrew.cooper3 at citrix dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|analyzer                    |c

--- Comment #4 from Andrew Cooper <andrew.cooper3 at citrix dot com> ---
(In reply to Andreas Schwab from comment #3)
> Perhaps it works if you declare the register variable in file scope.

Huh.  I honestly expected that not to compile, but it appears to, and it
appears to work.

There is minor perturbation in the build, but as far as I can see, it's just
slightly different register/instruction scheduling.

Why does being at global scope change the diagnostic?=