public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109720] -Wmaybe-uninitialized triggering when I can see no path that would allow it
Date: Wed, 03 May 2023 20:59:14 +0000	[thread overview]
Message-ID: <bug-109720-4-HPz2dcaz4Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109720-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Paul Smith from comment #1)
> Hm, maybe it's due to the union.  Maybe GCC can't grok that we ensure that
> we only use the dynamic_bitset leg of the union after we've initialized it?

Once we get the preprocessed source, it should be easy to figure out why the
warning is showing up and if it is related to unions or something else.

  parent reply	other threads:[~2023-05-03 20:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 20:40 [Bug c++/109720] New: " psmith at gnu dot org
2023-05-03 20:56 ` [Bug tree-optimization/109720] " psmith at gnu dot org
2023-05-03 20:59 ` pinskia at gcc dot gnu.org [this message]
2023-05-03 21:39 ` psmith at gnu dot org
2023-05-03 21:58 ` pinskia at gcc dot gnu.org
2023-05-04 11:28 ` rguenth at gcc dot gnu.org
2023-05-04 13:23 ` psmith at gnu dot org
2023-05-15 21:44 ` psmith at gnu dot 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-109720-4-HPz2dcaz4Q@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).