public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-101770-4-g0uY44Yxnz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101770-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101770

Paul Eggert <eggert at cs dot ucla.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED
            Version|11.2.1                      |13.1.1

--- Comment #4 from Paul Eggert <eggert at cs dot ucla.edu> ---
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 the
Target Milestone being 13.0.

The symptoms are:

$ gcc -O2 -Wmaybe-uninitialized -S w.i
w.i: In function ‘edit’:
w.i:50:18: warning: ‘cmd1’ may be used uninitialized [-Wmaybe-uninitialized]
   50 |           return !cmd1;
      |                  ^~~~~
w.i:7:11: note: ‘cmd1’ 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.

  parent reply	other threads:[~2023-05-19 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 23:50 [Bug tree-optimization/101770] New: " eggert at cs dot ucla.edu
2021-08-04  6:34 ` [Bug tree-optimization/101770] " rguenth at gcc dot gnu.org
2021-08-05 14:59 ` msebor at gcc dot gnu.org
2022-11-20  5:00 ` law at gcc dot gnu.org
2022-11-28 22:36 ` pinskia at gcc dot gnu.org
2023-05-19 21:16 ` eggert at cs dot ucla.edu [this message]
2023-05-19 21:44 ` eggert at cs dot ucla.edu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101770-4-g0uY44Yxnz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).