From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A10F03858C78; Wed, 3 May 2023 21:58:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A10F03858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683151080; bh=sL9xtFNFuaC//2pjDKsjnm+NCEqY7d4ysDyfPAicS58=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uI7TrBLiMVeMeVINC6N9qHfTQsI5q5bDdB4MnMg8UrX9hef/uFORElrOu+vv42qKR gMwl3BGX36pMk4u8hBoXuD4J0OE/TKjvLD2jxX6y118yNHfsoGbAyIcehspNLsJlW3 LjZ4oW7rCLOj9Bd4UaCxmglqb1NcPIBtPiIuy9sU= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109720] -Wmaybe-uninitialized triggering when I can see no path that would allow it Date: Wed, 03 May 2023 21:58:00 +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: 13.1.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: 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=3D109720 --- Comment #4 from Andrew Pinski --- Some internal GCC Notes: PRE introduces the read from uninitialized memory though it is not used in = some pathes. The IR/CFG is very has some interesting twists and turns to it which looks like it confuses both PRE and the uninitialized warning code.=