public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95825] [10/11/12/13 Regression] boost::optional -Wuninitialized with -fsanitize=address
Date: Mon, 17 Apr 2023 08:22:15 +0000	[thread overview]
Message-ID: <bug-95825-4-v4s3RFb5eb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95825-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
(In reply to daniel.klauer from comment #7)
> Reduced test case:
> 
> 
> template<typename T>
> struct tc_optional_base
> {
> 	// default ctor leaves m_storage uninitialized
> 	tc_optional_base() : m_initialized(false) {}
> 	bool m_initialized;
> 	T m_storage;
> };

This example seems unrelated to the issue, because you have here a struct, not
a union.

  parent reply	other threads:[~2023-04-17  8:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 19:31 [Bug c++/95825] New: [7/8/9/10/11 Regression] boost::optional -Wuninitialized nok.raven at gmail dot com
2020-06-23  6:58 ` [Bug c++/95825] [8/9/10/11 " rguenth at gcc dot gnu.org
2020-08-04 16:51 ` [Bug tree-optimization/95825] " mpolacek at gcc dot gnu.org
2020-10-12 12:53 ` rguenth at gcc dot gnu.org
2021-05-14  9:53 ` [Bug tree-optimization/95825] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:17 ` rguenth at gcc dot gnu.org
2022-05-27  9:42 ` [Bug tree-optimization/95825] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2022-09-22 13:13 ` [Bug tree-optimization/95825] [10/11/12/13 Regression] boost::optional -Wuninitialized with -fsanitize=address rguenth at gcc dot gnu.org
2023-04-17  8:15 ` daniel.klauer at gin dot de
2023-04-17  8:22 ` daniel.kruegler at googlemail dot com [this message]
2023-04-17  8:46 ` daniel.klauer at gin dot de
2023-07-07 10:37 ` [Bug tree-optimization/95825] [11/12/13/14 " 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-95825-4-v4s3RFb5eb@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).