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/105749] Bogus maybe-unitialized when using std::optional, regex and sstream
Date: Wed, 22 Jun 2022 20:20:21 +0000 [thread overview]
Message-ID: <bug-105749-4-mWagLg6X5G@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105749-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105749
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Interesting that commenting unrelated parts or changing them slightly makes
warning go away.
Most likely inlining changes with those being there vs not being there.
next prev parent reply other threads:[~2022-06-22 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:13 [Bug c++/105749] New: " hi+gccbugs at yamlcoder dot me
2022-06-22 20:20 ` pinskia at gcc dot gnu.org [this message]
2022-06-22 20:23 ` [Bug tree-optimization/105749] " pinskia at gcc dot gnu.org
2022-06-22 20:24 ` pinskia at gcc dot gnu.org
2022-09-22 13:25 ` rguenth 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-105749-4-mWagLg6X5G@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).