public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krax.powah at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102401] New: std::bit_cast falls over, seemingly due to some invisible alignment requirements
Date: Sat, 18 Sep 2021 16:25:08 +0000	[thread overview]
Message-ID: <bug-102401-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102401
           Summary: std::bit_cast falls over, seemingly due to some
                    invisible alignment requirements
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: krax.powah at gmail dot com
  Target Milestone: ---

GCC Version: The current truck (12.0.0 20210917), but also present on all
versions which support std::bit_cast.

Repro case (https://godbolt.org/z/zWbMnMfvx):

```
    #include <bit>

    struct Item
    {
        float a = 0;
        float b = 0;
        char  c = 0;  // Removing this or changing it to type with a size of 4
    };                // fixes it.

    struct M
    {
        struct Data { char d[sizeof(Item)]; };
        static constexpr Data build(Item item)
        {
            Data d {};
            d = std::bit_cast<Data>(item);
            return d;
        }
    };

    int main(void)
    {
        constexpr auto data = M::build({}); // Only occurs if this is a
constexpr assignment
    }
```

Result:

```
    In file included from <source>:1:
    /opt/compiler-explorer/gcc-trunk-20210917/include/c++/12.0.0/bit: In
function 'int main()':
    <source>:26:35:   in 'constexpr' expansion of 'M::build(Item{(float)0,
(float)0, '\000'})'
    <source>:18:32:   in 'constexpr' expansion of 'std::bit_cast<M::Data,
Item>(item)'
    /opt/compiler-explorer/gcc-trunk-20210917/include/c++/12.0.0/bit:77:33:
error: '__builtin_bit_cast' accessing uninitialized byte at offset 9
       77 |       return __builtin_bit_cast(_To, __from);
          |                                 ^~~
    ASM generation compiler returned: 1
    In file included from <source>:1:
    /opt/compiler-explorer/gcc-trunk-20210917/include/c++/12.0.0/bit: In
function 'int main()':
    <source>:26:35:   in 'constexpr' expansion of 'M::build(Item{(float)0,
(float)0, '\000'})'
    <source>:18:32:   in 'constexpr' expansion of 'std::bit_cast<M::Data,
Item>(item)'
    /opt/compiler-explorer/gcc-trunk-20210917/include/c++/12.0.0/bit:77:33:
error: '__builtin_bit_cast' accessing uninitialized byte at offset 9
       77 |       return __builtin_bit_cast(_To, __from);
          |                                 ^~~
    Execution build compiler returned: 1
```

             reply	other threads:[~2021-09-18 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 16:25 krax.powah at gmail dot com [this message]
2021-09-18 16:33 ` [Bug c++/102401] " jakub at gcc dot gnu.org
2021-09-18 18:47 ` pinskia at gcc dot gnu.org
2021-09-18 18:55 ` jakub at gcc dot gnu.org
2021-09-18 22:23 ` redi at gcc dot gnu.org
2021-09-20  9:15 ` jakub at gcc dot gnu.org
2021-09-20  9:41 ` redi at gcc dot gnu.org
2022-01-12 20:08 ` jakub 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-102401-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).