From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How to stop gcc padding structs???
Date: Mon, 29 Jan 2001 09:53:00 -0000 [thread overview]
Message-ID: <20010129115707.A12269@visi.com> (raw)
In-Reply-To: <3A75AD28.3F252CD3@redhat.com>
On Mon, Jan 29, 2001 at 05:49:28PM +0000, Jonathan Larmour wrote:
> It's generally non-portable to rely on struct layout matching
> hardware, and just because gcc can be coerced to do it doesn't
> make it wise, nor guarantee it on different architectures (or
> different versions of gcc!). It is better practice to use
> accessor macros instead.
>
> And no, I know Red Hat don't always practice what we preach,
> but we *should*.
I know, but debugging is a royal pain when GDB doesn't know
about the structure of the peripheral and you've got to work
off of hex memory dumps just like the bad old days.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-01-29 9:53 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
2001-01-29 9:49 ` Jonathan Larmour
2001-01-29 9:53 ` Grant Edwards [this message]
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=20010129115707.A12269@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).