From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How to stop gcc padding structs???
Date: Mon, 29 Jan 2001 07:24:00 -0000 [thread overview]
Message-ID: <20010129092833.A11509@visi.com> (raw)
In-Reply-To: <20010129092709.A13176@biferten.ma.tech.ascom.ch>
On Mon, Jan 29, 2001 at 09:27:09AM +0100, Andrew Lunn wrote:
> On Sun, Jan 28, 2001 at 12:40:59PM -0600, Grant Edwards wrote:
> >
> > I'm again fighting with gcc trying (and failing) to get it to
> > stop putting padding bytes into structs. Have any eCosians
> > figured out how to prevent gcc from padding structs?
>
> Yes, but more by luck combined with trial and error than anything
> else. When you have this sort of structure in structre arrangement i
> find it best to work upwards. Make sure sizeof(high) is realy 2.
It's 4, and nothing I try with __attribute__((packed)) will make it 2.
I'll mess with alignement attributes some.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-01-29 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 10:37 Grant Edwards
2001-01-29 0:27 ` Andrew Lunn
2001-01-29 7:24 ` Grant Edwards [this message]
2001-01-29 9:49 ` Jonathan Larmour
2001-01-29 9:53 ` Grant Edwards
2001-01-29 14:15 ` Jesper Skov
2001-01-28 13:34 Lewin A.R.W. Edwards
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=20010129092833.A11509@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.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).