public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80548] -Wmaybe-uninitialized false positive when an assignment is added
Date: Mon, 21 Nov 2022 14:40:52 +0000	[thread overview]
Message-ID: <bug-80548-4-HogddxkxPH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80548-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jeffrey A. Law <law at gcc dot gnu.org> ---
These warnings are certainly sensitive to all kinds of things, so it's possible
it's just gone latent.  The only way to be sure would be to bisect all the work
between gcc-12 and the trunk and pour over the dumps with a fine tooth comb. I
would hazard a guess it was Aldy's backwards threader work, particularly around
not bailing out too early for subpaths based on comments in the BZ, but one
would have to bisect to be 100% sure.

What I would recommend would be opening a new bug for the new cases.  While
these bugs often appear to be the same, it's actually fairly rare in practice
that they have the same underlying cause.  Each has to be analysed
individually.

  parent reply	other threads:[~2022-11-21 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80548-4@http.gcc.gnu.org/bugzilla/>
2021-04-13 23:56 ` [Bug middle-end/80548] " msebor at gcc dot gnu.org
2021-11-30 14:09 ` [Bug tree-optimization/80548] " aldyh at gcc dot gnu.org
2021-11-30 14:20 ` aldyh at gcc dot gnu.org
2021-11-30 14:38 ` aldyh at gcc dot gnu.org
2021-12-01 16:03 ` aldyh at gcc dot gnu.org
2022-11-20  4:05 ` law at gcc dot gnu.org
2022-11-21  9:59 ` vincent-gcc at vinc17 dot net
2022-11-21 14:40 ` law at gcc dot gnu.org [this message]
2022-11-22 10:07 ` vincent-gcc at vinc17 dot net
2022-11-22 13:10 ` law at gcc dot gnu.org
2022-11-23 16:46 ` vincent-gcc at vinc17 dot net

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