From: Tim Hollebeek <tim@hollebeek.com>
To: Richard Henderson <rth@redhat.com>,
Mark Mitchell <mark@codesourcery.com>,
"David S. Miller" <davem@redhat.com>,
"gdr@integrable-solutions.net" <gdr@integrable-solutions.net>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: C ABI: struct/union inconsistency
Date: Sat, 28 Sep 2002 10:38:00 -0000 [thread overview]
Message-ID: <20020928100655.A10847@hollebeek.com> (raw)
In-Reply-To: <20020928014605.GA29853@redhat.com>
On Fri, Sep 27, 2002 at 06:46:05PM -0700, Richard Henderson wrote:
> On Fri, Sep 27, 2002 at 06:11:37PM -0700, Mark Mitchell wrote:
> > >How about "invisible", we're making the zero sized members
> > >invisible :-)
> >
> > That's cute.
>
> Cute, but not very descriptive. allow_zero_size?
Don't we already have (or recently discuss) an attribute to eliminate
tail padding? Shouldn't that get used here?
sizeof(struct __attribute__(no_tail_padding) { } ) == 0
seems intuitive to me.
-Tim
next prev parent reply other threads:[~2002-09-28 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 8:59 Mark Mitchell
2002-09-27 9:33 ` Joseph S. Myers
2002-09-27 10:09 ` Richard Henderson
2002-09-27 10:31 ` Mark Mitchell
2002-09-27 11:41 ` Richard Henderson
2002-09-27 11:54 ` Gabriel Dos Reis
2002-09-27 13:44 ` Mark Mitchell
2002-09-27 15:11 ` Richard Henderson
2002-09-27 15:18 ` Mark Mitchell
2002-09-27 16:26 ` Richard Henderson
2002-09-27 17:53 ` Mark Mitchell
2002-09-27 18:51 ` David S. Miller
2002-09-27 19:01 ` Mark Mitchell
2002-09-27 19:54 ` Richard Henderson
2002-09-28 10:38 ` Tim Hollebeek [this message]
2002-09-28 12:56 ` Mark Mitchell
2002-09-28 13:00 ` Richard Henderson
2002-09-28 13:52 ` Mark Mitchell
2002-09-30 9:20 ` Gabriel Paubert
2002-09-30 10:22 ` Gabriel Dos Reis
2002-09-28 16:55 ` Per Bothner
2002-09-29 2:40 ` Tim Hollebeek
2002-09-27 20:02 ` Michael S. Zick
2002-09-28 9:01 ` Fergus Henderson
2002-09-27 20:43 ` Hans-Peter Nilsson
2002-09-28 16:55 ` Alexandre Oliva
2002-09-28 7:02 Robert Dewar
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=20020928100655.A10847@hollebeek.com \
--to=tim@hollebeek.com \
--cc=davem@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=mark@codesourcery.com \
--cc=rth@redhat.com \
/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).