public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc@nieper-wisskirchen.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86465] [9/10/11/12 Regression] C++17 <optional> triggers: ‘<anonymous>’ may be used uninitialized in this function
Date: Wed, 12 Jan 2022 12:12:10 +0000 [thread overview]
Message-ID: <bug-86465-4-g4CjwML2VY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86465-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86465
Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marc@nieper-wisskirchen.de
--- Comment #18 from Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de> ---
Does a viable workaround exist that doesn't amount to disabling the warning
option altogether?
In my case, the actual warning is triggered inside the standard library, which
is used by my code that uses std::optional.
Thanks.
next prev parent reply other threads:[~2022-01-12 12:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86465-4@http.gcc.gnu.org/bugzilla/>
2020-10-27 14:45 ` [Bug c++/86465] [8/9/10/11 " redi at gcc dot gnu.org
2020-11-16 21:09 ` redi at gcc dot gnu.org
2021-04-08 16:08 ` [Bug tree-optimization/86465] " jason at gcc dot gnu.org
2021-05-14 9:50 ` [Bug tree-optimization/86465] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:11 ` rguenth at gcc dot gnu.org
2022-01-12 9:59 ` geoff3jones at googlemail dot com
2022-01-12 10:16 ` geoff3jones at googlemail dot com
2022-01-12 10:22 ` marc@nieper-wisskirchen.de
2022-01-12 12:12 ` marc@nieper-wisskirchen.de [this message]
2022-05-27 9:39 ` [Bug tree-optimization/86465] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:35 ` jakub at gcc dot gnu.org
2022-09-22 13:11 ` 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-86465-4-g4CjwML2VY@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).