public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gnubug@skilbeck.com To: gcc-gnats@gcc.gnu.org Subject: c++/6874: deriving from zero-sized objects causes extraneous padding Date: Thu, 30 May 2002 16:06:00 -0000 [thread overview] Message-ID: <20020530203200.1081.qmail@sources.redhat.com> (raw) >Number: 6874 >Category: c++ >Synopsis: deriving from zero-sized objects causes extraneous padding >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Thu May 30 13:36:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: gnubug@skilbeck.com >Release: 2.95.?? >Organization: >Environment: mips >Description: when deriving from a zero-sized struct, can we get the dummy single byte overlaid by the data members of the derived struct? >How-To-Repeat: struct Bob { void *operator new(size_t s); void operator delete(void *p); }; struct Bill : Bob { int Jack; }; ... sizeof(Bob) == 1 (Fine) sizeof(Bill) == 8 (sizeof(int) would be nice, like other compilers) >Fix: er... hack the gcc!? >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-05-30 20:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-30 16:06 gnubug [this message] 2002-06-07 7:25 lerdsuwa 2002-06-07 19:06 Charlie Skilbeck
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=20020530203200.1081.qmail@sources.redhat.com \ --to=gnubug@skilbeck.com \ --cc=gcc-gnats@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).