public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at ebasoft dot com.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104386] New: no_unique_address causes invalid member alignment of pod struct
Date: Fri, 04 Feb 2022 17:43:43 +0000	[thread overview]
Message-ID: <bug-104386-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104386
           Summary: no_unique_address causes invalid member alignment of
                    pod struct
           Product: gcc
           Version: 11.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gcc at ebasoft dot com.pl
  Target Milestone: ---

struct base
{ [[no_unique_address]]
 uint32_t x; std::byte v;
 };
struct foo : public base
 { std::byte z; };

gcc sizeof(foo) == 8 https://godbolt.org/z/G4Mo3PdKT

clang sizeof(foo) == 12 https://godbolt.org/z/bdzvaMn9c

As I was told it is gcc bug 
https://www.reddit.com/r/cpp/comments/sjx2mk/no_unique_addres_where_can_in_c_standard_instead/

[orbital1337]"Your class base is a POD but its not a POD for the purpose of
layout (since it has potentially overlapping data members). Thus the Itanium
ABI specifies that it's size without padding (dsize) should be set to its size
with padding (sizeof). The first datamember of your class foo is put at
dsize(base). clang does the right thing and puts it at an offset of 8 bytes
whereas gcc ignores that one line of the specification and puts it at an offset
of 5 bytes instead."

             reply	other threads:[~2022-02-04 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 17:43 gcc at ebasoft dot com.pl [this message]
2022-02-04 21:55 ` [Bug c++/104386] " pinskia at gcc dot gnu.org
2022-02-06 10:26 ` gcc at ebasoft dot com.pl
2022-02-06 23:10 ` pinskia at gcc dot gnu.org
2022-03-29 15:05 ` redi 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-104386-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).