public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99637] New: bit_cast doesn't work with padding bits and it should
Date: Wed, 17 Mar 2021 20:46:44 +0000	[thread overview]
Message-ID: <bug-99637-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99637
           Summary: bit_cast doesn't work with padding bits and it should
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hanicka at hanicka dot net
  Target Milestone: ---

Standard states in https://eel.is/c++draft/bit.cast#2 "Padding bits of the
result are unspecified."

Current trunk GCC (11.0.1 20210316) gives error in presence of padding bits:

https://compiler-explorer.com/z/MhKMb5

```
struct my_field
{
    // change size to 64 and it will work
    unsigned long long a : 63;
};

constexpr unsigned long long get_value(const auto & val) noexcept {
    static_assert(sizeof(val) == sizeof(unsigned long long));

    return __builtin_bit_cast(unsigned long long, val);
}

constexpr auto f = my_field{0};
constexpr auto v = get_value(f);
```

this is the error message GCC gives, but this shouldn't be a hard error

```
<source>:14:29:   in 'constexpr' expansion of 'get_value<my_field>(f)'
<source>:10:31: error: '__builtin_bit_cast' accessing uninitialized byte at
offset 7
   10 |     return __builtin_bit_cast(unsigned long long, val);
```

             reply	other threads:[~2021-03-17 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:46 hanicka at hanicka dot net [this message]
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
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@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).