public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103681] [9/10/11/12 Regression] Unusual behavior for tail padding with different c++ standards and NSDMI Date: Mon, 13 Dec 2021 19:02:52 +0000 [thread overview] Message-ID: <bug-103681-4-PolBPCOVWe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103681-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103681 --- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> --- compile-time testcase struct A { long l; char c = -1; }; struct B : public A { char d; }; #define SA(X) static_assert(X,#X) SA(sizeof (B) == sizeof (A) || alignof (long) < 2*sizeof(char));
next prev parent reply other threads:[~2021-12-13 19:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-13 12:24 [Bug other/103681] New: Unusual behavior for tail padding with different c++ standards n.deshmukh at samsung dot com 2021-12-13 12:26 ` [Bug other/103681] " pinskia at gcc dot gnu.org 2021-12-13 12:58 ` [Bug c++/103681] [9/10/11/12 Regression] Unusual behavior for tail padding with different c++ standards and NSDMI pinskia at gcc dot gnu.org 2021-12-13 18:55 ` jason at gcc dot gnu.org 2021-12-13 19:02 ` jason at gcc dot gnu.org [this message] 2021-12-14 18:43 ` jason at gcc dot gnu.org 2021-12-17 3:27 ` cvs-commit at gcc dot gnu.org 2021-12-17 20:42 ` [Bug c++/103681] [9/10/11 " jason at gcc dot gnu.org 2022-01-21 17:06 ` cvs-commit at gcc dot gnu.org 2022-05-13 15:27 ` jason 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-103681-4-PolBPCOVWe@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).