public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ed at catmur dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111094] Spurious Wuninitialized swapping underlying bytes of object representation in move constructor Date: Mon, 21 Aug 2023 19:59:20 +0000 [thread overview] Message-ID: <bug-111094-4-EyHwBKS3Nr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111094-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111094 Ed Catmur <ed at catmur dot uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Ed Catmur <ed at catmur dot uk> --- Well, I feel like [basic.types.general] probably allows it. But regardless, yeah, this is an opt-in diagnostic so it's fine if gcc warns on things that are legal but dubious. We'll just have to be a bit smarter in how we write this code. Thanks again.
prev parent reply other threads:[~2023-08-21 19:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-21 19:26 [Bug c++/111094] New: " ed at catmur dot uk 2023-08-21 19:33 ` [Bug tree-optimization/111094] " pinskia at gcc dot gnu.org 2023-08-21 19:34 ` pinskia at gcc dot gnu.org 2023-08-21 19:43 ` pinskia at gcc dot gnu.org 2023-08-21 19:59 ` ed at catmur dot uk [this message]
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-111094-4-EyHwBKS3Nr@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).