public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederik Deweerdt <deweerdt@free.fr>
To: Phil Endecott <phil_arcwk_endecott@chezphil.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Subtleties of __attribute__((packed))
Date: Wed, 6 Dec 2006 14:01:38 +0000	[thread overview]
Message-ID: <20061206140138.GA16350@slug> (raw)
In-Reply-To: <1165411241721@dmwebmail.belize.chezphil.org>

On Wed, Dec 06, 2006 at 01:20:41PM +0000, Phil Endecott wrote:
> Dear All,
> 
> I used to think that this:
> 
> struct foo {
>   int a  __attribute__((packed));
>   char b __attribute__((packed));
>   ... more fields, all packed ...
> };
> 
> was exactly the same as this:
> 
> struct foo {
>   int a;
>   char b;
>   ... more fields ...
> } __attribute__((packed));
> 
> but it is not, in a subtle way.
> 
This is likely a gcc bug isn't it? The gcc info page states:
  Specifying this attribute for `struct' and `union' types is
  equivalent to specifying the `packed' attribute on each of the
  structure or union members.

Regards,
Frederik

  reply	other threads:[~2006-12-06 14:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 13:20 Subtleties of __attribute__((packed)) Phil Endecott
2006-12-06 14:01 ` Frederik Deweerdt [this message]
2006-12-06 14:24   ` Phil Endecott
2006-12-06 15:04 ` Jan Blunck
2006-12-06 15:22   ` Phil Endecott
2006-12-06 15:54     ` Jan Blunck
2006-12-06 16:02       ` Andreas Schwab
2006-12-06 16:41         ` Jan Blunck
2006-12-06 17:28           ` Andreas Schwab
2006-12-06 16:13       ` Phil Endecott
2006-12-06 16:26         ` Jan Blunck
2006-12-06 17:54       ` Russell King
2006-12-06 18:05         ` David Miller
2006-12-07  9:48         ` Jan Blunck
2006-12-07 10:30           ` Andreas Schwab

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=20061206140138.GA16350@slug \
    --to=deweerdt@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil_arcwk_endecott@chezphil.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