git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Gerrit Pape <pape@smarden.org>, git@vger.kernel.org
Subject: Re: sizeof(struct ...)
Date: Thu, 23 Nov 2006 16:45:09 +0100	[thread overview]
Message-ID: <4565C205.8050300@lsrfire.ath.cx> (raw)
In-Reply-To: <4565A866.8020201@shadowen.org>

Andy Whitcroft schrieb:
> This structure represents an on-disk/on-the-wire thing, should we not be
> specifying it in some architecture neutral way?  You are going to get
> the length right in the case of tail padding but not in the face of any
> other padding internally.
> 
> You see packing attributes applied to similar things in the kernel.
> Perhaps they are relevant here?
> Is there not some kind of attribute thing we can apply to this structure
> to prevent the padding?  You see that in the kernel from time to time.
> 
> struct foo {
> } __attribute__((packed));

Yes, that would be nice, but unfortunately __attribute__ is no standard
C.  Is there really a compiler that inserts padding between arrays of
unsigned chars?

Thanks,

  reply	other threads:[~2006-11-23 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 10:16 sizeof(struct ...) Gerrit Pape
2006-11-23 12:43 ` René Scharfe
2006-11-23 13:38   ` René Scharfe
2006-11-23 13:55     ` Andy Whitcroft
2006-11-23 15:45       ` René Scharfe [this message]
2006-11-23 15:54         ` Erik Mouw
2006-11-23 16:14           ` René Scharfe
2006-11-23 16:19             ` Andy Whitcroft
2006-11-23 17:57               ` René Scharfe
2006-11-23 16:42             ` Erik Mouw
2006-11-23 20:47   ` Junio C Hamano
2006-11-23 22:02     ` [PATCH] archive-zip: don't use " René Scharfe
2006-11-24  8:53       ` Gerrit Pape

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=4565C205.8050300@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=apw@shadowen.org \
    --cc=git@vger.kernel.org \
    --cc=pape@smarden.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 NNTP newsgroup(s).