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 B82063858020; Mon, 21 Nov 2022 09:59:15 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B82063858020
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669024755;
	bh=hrGb7DIVY08aHDx/Fv9Km4Kuj9Va/DX++g5nBwKt2hQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=SDjFbIW/xfTU4k5wreK7ialHXt1BBKf1elUIMq+49x6UmfqZYRdQYmSq9glhC5VRC
	 /h3SWctGBU7eBsnc3zi0yikG8qMBx6zWDIzmBb9nhj3swN2G46eVAjn8H/033Rx59E
	 Gaie7rzs5EMeG9KfdLOaYRXcolcvGI5py9r56Q+g=
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80548] -Wmaybe-uninitialized false positive
 when an assignment is added
Date: Mon, 21 Nov 2022 09:59:13 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-80548-4-5MuxcRtNCi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80548-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80548-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=3D80548

--- Comment #8 from Vincent Lef=C3=A8vre <vincent-gcc at vinc17 dot net> ---
Indeed, compared to GCC 12.2.0, the trunk no longer warns on the simple
testcase I provided. However, I cannot see any change of the warnings on my
original file (to myself: tmd/binary32/hrcases.c), except concerning the or=
der
of the warnings (on this file, I get 2 spurious -Wmaybe-uninitialized warni=
ngs,
and they are now reversed). I'll try to provide another simple testcase.

I'm wondering whether this bug is really fixed or it just happens to have
disappeared on the testcase just because of a side effect of some other cha=
nge
in GCC and a small change addition to the testcase would make it reappear.=