This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Yet another ARM alignment question
- To: Wilson Kwan <wilson at kinesphere dot com>
- Subject: Re: [ECOS] Yet another ARM alignment question
- From: elf at florence dot buici dot com
- Date: Tue, 24 Apr 2001 21:03:14 -0700
- Cc: ecos-discuss at sources dot redhat dot com
- References: <008101c0cd3b$0e339540$0b02a8c0@obiwan>
IIRC, the compilers are supposed to align correctly for the given
architecture. In fact, if you want to pack against it's better
judgement, you need to use the __ALIGNMENT__ (__ALIGN__?) directive.
On Tue, Apr 24, 2001 at 11:51:49PM -0400, Wilson Kwan wrote:
> I've read through the eCos list regarding ARM alignment problems and am
> wondering if anyone out there can lend a few suggestions. I am faced with a
> general porting problem of some legacy Intel code. Of course all the
> structures were packed on byte boundaries and with some having structures
> within structures.
>
> My question is has anyone solved the word and dword alignment problems on
> ARM? Is is any combination of gcc compiler options that will overcome this
> limitation albeit at a performance cost. What about an alignment trap
> handler? Anyone have any sample code on how to write one of these or a
> pointer to some good documentation?
>
> Thanks again in advance,
>
> Wilson