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 c++/111771] Incorrect "is used uninitialized" warning, as if zero-initialization didn't propagate through user-provided default constructors Date: Thu, 12 Oct 2023 07:29:33 +0000 [thread overview] Message-ID: <bug-111771-4-AcjvFHAugN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111771-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111771 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2023-10-12 Keywords| |diagnostic, wrong-code Status|UNCONFIRMED |NEW CC| |jason at gcc dot gnu.org Known to fail| |13.2.1, 7.5.0 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- We have int main () { int D.2848; { struct B b; try { b.D.2778.x = 0; B::B (&b); D.2848 = b.D.2778.x; return D.2848; but: void B::B (struct B * const this) { _1 = &this->D.2778; A::A (_1); } void A::A (struct A * const this) { *this = {CLOBBER}; so A::A invoked by B::B invalidates the initialized storage. Maybe a "different" B::B should have been called (one not invoking A::A?).
next prev parent reply other threads:[~2023-10-12 7:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 14:42 [Bug c++/111771] New: " iamsupermouse at mail dot ru 2023-10-11 17:17 ` [Bug c++/111771] " pinskia at gcc dot gnu.org 2023-10-12 5:17 ` iamsupermouse at mail dot ru 2023-10-12 7:29 ` rguenth at gcc dot gnu.org [this message] 2023-10-12 7:30 ` rguenth at gcc dot gnu.org 2023-10-12 16:34 ` 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-111771-4-AcjvFHAugN@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: linkBe 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).