public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107206] Bogus -Wuninitialized in std::optional
Date: Tue, 11 Oct 2022 10:22:19 +0000	[thread overview]
Message-ID: <bug-107206-4-cIn1S8otoQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107206-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, in other places I saw it's very much wanted to scalarize std::optional
because that's often the best way to figure whether it's engaged or not and
optimize dead code based on that.  So not scalarizing probably isn't the best
answer, still it would be nice to understand why SRA picks 'int' here even
though there's no access of that.

  parent reply	other threads:[~2022-10-11 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 23:14 [Bug c++/107206] New: " ed at catmur dot uk
2022-10-11  8:16 ` [Bug libstdc++/107206] " rguenth at gcc dot gnu.org
2022-10-11 10:10 ` redi at gcc dot gnu.org
2022-10-11 10:20 ` rguenth at gcc dot gnu.org
2022-10-11 10:22 ` rguenth at gcc dot gnu.org [this message]
2022-10-14 16:53 ` [Bug tree-optimization/107206] " jamborm at gcc dot gnu.org
2022-10-16 17:27 ` rguenther at suse dot de
2022-10-19 12:59 ` cvs-commit at gcc dot gnu.org
2022-11-16 12:13 ` cvs-commit at gcc dot gnu.org
2022-11-16 12:14 ` jamborm at gcc dot gnu.org
2022-11-28 22:22 ` 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-107206-4-cIn1S8otoQ@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).