This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Ignore earlier dumb question, but here is another
- To: "Lewin A.R.W. Edwards" <larwe at larwe dot com>
- Subject: RE: [ECOS] Ignore earlier dumb question, but here is another
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Tue, 09 Jan 2001 06:53:21 -0700 (MST)
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat, Inc.
On 09-Jan-2001 Lewin A.R.W. Edwards wrote:
> Hi Gary,
>
>> > told me the correct switch to use. I've recompiled eCos with -fpack-struct
>> > and all is seemingly well. However I worry that the OS might not have been
>> > tested in this configuration. Any known caveats?
>>
>>I have tried it when building network code. It doesn't break antyhing, AFAIK,
>>but it also may not always do just what you want. YMMV
>
> Do you by chance have an alternate suggestion? Really the only part of my
> code that needs this functionality is the filesystem (and my JPEG codec).
> There must be a mechanism for accomplishing what I need.
>
> I did try a "composite build" wherein my code was compiled with packed
> structures and eCos was compiled with aligned structures, and it DID work,
> but that's probably because I'm not using any OS functionality at all.
Look at the networking code. We use __attribute__(pack) on the structures
which matter and it works just fine. It avoids the "big hammer" which often
does not function as intended.