From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas To: "Lewin A.R.W. Edwards" Cc: ecos-discuss@sources.redhat.com Subject: RE: [ECOS] Ignore earlier dumb question, but here is another Date: Tue, 09 Jan 2001 05:53:00 -0000 Message-id: References: <4.3.2.7.2.20010108191921.00ae8ac0@larwe.com> X-SW-Source: 2001-01/msg00115.html 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.