From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B6D58384AB4A; Tue, 7 May 2024 18:45:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B6D58384AB4A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1715107517; bh=vAvswqBPUfVrzVZWh+X30NrVKWrk+vszfRLWps66uig=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZT4GrwZIc2hz9Y/cGF5m6utaaFswhwZdhu+DFNwymVp/Avg8lchmHrs/QMeOO3KZ9 OpbOPWm8BfmvINsf5gMMslcrjg6iJfIYterN4zLvj0djT5gMZcFvuL35Wuq2jXUlE4 yv5tkRIC2PRSLBMdB0m74kyc214ogkStme1bxdZM= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114952] False positive -Wmaybe-uninitialized starting at -O3 in libbpf Date: Tue, 07 May 2024 18:45:17 +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: 14.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=3D114952 --- Comment #3 from Andrew Pinski --- Note I don't think this is a `False positive` exactly because GCC has no knowledge that errno could be non-zero after a fail call to open.=