From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E62F53858C41; Fri, 19 May 2023 21:16:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E62F53858C41 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684530990; bh=HJKUbQTUeL8k2Zi1KJxSldUpiKr6ssojSN7b+yjXql4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MrxttsYL5gzYfXLWOoSYfRSlbYZ6Rw9Vn/Vis95lunYJ4dV+KZT3JXN9F6g7meZ6S 27JOk9iufgJG5GPDJ/9ow8N/UDn+wDw1IZfhWZPI3+h4JNqI1GSnAteaJow8eFXvc0 SiC7L+jKuFVradmHL9zmXX6rdZcr5E7B+aaQq1hg= From: "eggert at cs dot ucla.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101770] -Wmaybe-uninitialized false alarm with only locals in GNU diffutils Date: Fri, 19 May 2023 21:16:30 +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.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: eggert at cs dot ucla.edu X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status version 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=3D101770 Paul Eggert changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED Version|11.2.1 |13.1.1 --- Comment #4 from Paul Eggert --- I seeing the bug with gcc (GCC) 13.1.1 20230511 (Red Hat 13.1.1-2) on x86-64 when compiling GNU diffutils, so although the bug was reported fixed on the trunk last year, it appears that the fix hasn't propagated GCC 13 despite t= he Target Milestone being 13.0. The symptoms are: $ gcc -O2 -Wmaybe-uninitialized -S w.i w.i: In function =E2=80=98edit=E2=80=99: w.i:50:18: warning: =E2=80=98cmd1=E2=80=99 may be used uninitialized [-Wmay= be-uninitialized] 50 | return !cmd1; | ^~~~~ w.i:7:11: note: =E2=80=98cmd1=E2=80=99 was declared here 7 | int cmd1; | ^~~~ This appears to be the same bug as before so I am taking the liberty of reopening the bug report.=