public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99637] bit_cast doesn't work with padding bits and it should Date: Thu, 18 Mar 2021 10:35:12 +0000 [thread overview] Message-ID: <bug-99637-4-4v3UogBj68@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99637-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99637 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yes. If the result type is a class type and the padding bits in the input correspond to unsigned char or std::byte subobjects in the result, that's OK (because the only parts with indeterminate values are byte-like types, the rest of the result is properly initialized). I think GCC is correct here.
next prev parent reply other threads:[~2021-03-18 10:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-17 20:46 [Bug c++/99637] New: " hanicka at hanicka dot net 2021-03-17 20:58 ` [Bug c++/99637] " jakub at gcc dot gnu.org 2021-03-17 21:19 ` hanicka at hanicka dot net 2021-03-17 21:22 ` jakub at gcc dot gnu.org 2021-03-17 21:23 ` redi at gcc dot gnu.org 2021-03-18 9:12 ` redi at gcc dot gnu.org 2021-03-18 9:19 ` jakub at gcc dot gnu.org 2021-03-18 10:35 ` redi at gcc dot gnu.org [this message] 2023-04-26 7:51 ` m.cencora at gmail dot com
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-99637-4-4v3UogBj68@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).