LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Blunck <jblunck@suse.de>
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 17:26:20 +0100 [thread overview]
Message-ID: <20061206162620.GA4942@hasse.suse.de> (raw)
In-Reply-To: <1165421636345@dmwebmail.belize.chezphil.org>
On Wed, Dec 06, Phil Endecott wrote:
>
> To see a difference with your example structs you need to compare these two:
>
> struct wibble1 {
> char c;
> struct bar1 b1;
> };
>
> struct wibble2 {
> char c;
> struct bar2 b2;
> };
>
> struct wibble1 w1 = { 1, { 2, {3,4,5} } };
> struct wibble2 w2 = { 1, { 2, {3,4,5} } };
>
> Can you try that with your compilers? I get:
>
As I expected, I get:
.file "packed2a.c"
.globl w1
.data
.align 2
.type w1, @object
.size w1, 14
w1:
.byte 1
.byte 2
.4byte 3
.byte 4
.zero 3
.4byte 5
.globl w2
.align 2
.type w2, @object
.size w2, 14
w2:
.byte 1
.byte 2
.4byte 3
.byte 4
.zero 3
.4byte 5
.ident "GCC: (GNU) 4.1.2 20060531 (prerelease) (SUSE Linux)"
.section .note.GNU-stack,"",@progbits
next prev parent reply other threads:[~2006-12-06 16:26 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
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 [this message]
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=20061206162620.GA4942@hasse.suse.de \
--to=jblunck@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).