From: Joe Buck <Joe.Buck@synopsys.com>
To: Richard.Earnshaw@arm.com
Cc: Joe.Buck@synopsys.COM (Joe Buck),
mark@codesourcery.com (Mark Mitchell),
gcc@gcc.gnu.org
Subject: Re: RFC: attribute "unpadded"
Date: Wed, 28 Aug 2002 11:20:00 -0000 [thread overview]
Message-ID: <200208281820.LAA09740@atrus.synopsys.com> (raw)
In-Reply-To: <200208281754.SAA07892@cam-mail2.cambridge.arm.com>
Richard Earnshaw:
> > > I wonder if we should not just give the type two sizes, an unpadded one
> > > and a padded one. Then the unpadded one would be used for operations such
Me:
> > That would violate C semantics: sizeof() must return the padded length.
> > If it did not, the common C idiom
Richard:
> We've already gone outside the realm of the C standard as soon as we
> define __attribute__ ((unpadded)).
You're right, I was confused. Objection withdrawn, pardon my stupidity.
On the other hand, there may be other problems with making arrays of unpadded
objects. It almost seems contractory: to find the address of foo[1] we
consider padding, but we've declared the thing unpadded.
next prev parent reply other threads:[~2002-08-28 11:20 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 10:43 Mark Mitchell
2002-08-23 10:49 ` Andrew Haley
2002-08-23 10:50 ` Mark Mitchell
2002-08-23 12:39 ` Andrew Haley
2002-08-23 13:02 ` Neil Booth
2002-08-23 13:20 ` Mark Mitchell
2002-08-23 15:57 ` Zack Weinberg
2002-08-25 19:03 ` Fergus Henderson
2002-08-25 23:59 ` Zack Weinberg
2002-08-26 4:52 ` language-independent types (was: RFC: attribute "unpadded") Fergus Henderson
2002-08-23 16:42 ` RFC: attribute "unpadded" Olivier Galibert
2002-08-25 18:16 ` Mark Mitchell
2002-08-23 10:51 ` Fergus Henderson
2002-08-23 10:53 ` Mark Mitchell
2002-08-23 21:52 ` Alexandre Oliva
2002-08-24 14:05 ` Paul Koning
2002-08-25 18:00 ` Mark Mitchell
2002-08-26 6:41 ` Paul Koning
2002-08-26 8:28 ` Andreas Schwab
2002-08-26 9:23 ` Gabriel Dos Reis
2002-08-26 9:45 ` Mark Mitchell
2002-08-26 10:54 ` Gabriel Dos Reis
2002-08-27 8:00 ` Fergus Henderson
2002-08-27 9:52 ` Tom Tromey
2002-08-27 10:46 ` Mark Mitchell
2002-08-27 11:39 ` Fergus Henderson
2002-08-27 12:01 ` Mark Mitchell
2002-08-27 12:04 ` Gabriel Dos Reis
2002-08-27 14:25 ` Joe Buck
2002-08-29 15:12 ` Richard Henderson
2002-08-29 15:10 ` Richard Henderson
2002-08-29 15:24 ` Richard Henderson
2002-08-29 15:30 ` Mark Mitchell
2002-08-29 16:30 ` Richard Henderson
2002-08-29 15:29 ` Mark Mitchell
2002-08-29 15:45 ` Gabriel Dos Reis
2002-08-29 16:00 ` Mark Mitchell
2002-08-29 16:06 ` Gabriel Dos Reis
2002-08-29 16:32 ` Richard Henderson
2002-08-29 16:49 ` Mark Mitchell
2002-08-30 0:12 ` Kai Henningsen
2002-08-26 19:10 ` Jamie Lokier
2002-08-27 0:03 ` Mark Mitchell
2002-08-28 3:50 ` Richard Earnshaw
2002-08-28 10:22 ` Joe Buck
2002-08-28 10:56 ` Richard Earnshaw
2002-08-28 11:20 ` Joe Buck [this message]
2002-08-29 2:07 ` Richard Earnshaw
2002-08-28 21:22 ` Fergus Henderson
2002-08-29 2:27 ` Richard Earnshaw
2002-08-23 10:58 Benjamin Kosnik
2002-08-23 11:05 ` Mark Mitchell
2002-08-23 11:14 ` Benjamin Kosnik
2002-08-23 11:34 ` Janis Johnson
2002-08-23 11:39 ` Mark Mitchell
2002-08-23 11:35 ` Mark Mitchell
2002-08-23 12:03 ` Benjamin Kosnik
2002-08-23 16:07 Richard Kenner
2002-08-27 14:43 Richard Kenner
2002-08-27 20:25 ` Fergus Henderson
2002-08-28 4:12 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=200208281820.LAA09740@atrus.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).