public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99756] New: bogus -Wmaybe-uninitialized with a use conditional that's a subset of a defining conditional
Date: Wed, 24 Mar 2021 23:48:19 +0000	[thread overview]
Message-ID: <bug-99756-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99756
           Summary: bogus -Wmaybe-uninitialized with a use conditional
                    that's a subset of a defining conditional
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

The following code triggers a spurious -Wmaybe-uninitialized.  There are two
underlying problems: one is a limitation of the uninitialized pass and another
is a missed optimization opportunity described in PR 99755 (the second test for
k results in another read from it instead of reusing the value read previously
in the first conditional).

$ cat t.c && gcc -O2 -S -Wall t.c
extern int a[], i, j, k;

void f (void)
{
  int x;
  if (i > 1 && j > 2 && k > 3)
    x = i + 1;

  if (i == 2 && j == 3 && k == 4)
    a[x] = 0;                 // { dg-bogus "Wmaybe-uninitialized" }
}

t.c: In function ‘f3’:
t.c:28:10: warning: ‘x’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
   28 |     a[x] = 0;                 // { dg-bogus "Wmaybe-uninitialized" }
      |     ~~~~~^~~

             reply	other threads:[~2021-03-24 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 23:48 msebor at gcc dot gnu.org [this message]
2021-03-24 23:51 ` [Bug tree-optimization/99756] " msebor at gcc dot gnu.org
2021-11-30 12:12 ` aldyh at gcc dot gnu.org
2021-12-18 11:47 ` pinskia at gcc dot gnu.org

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-99756-4@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).