Sorry for having replied just to you. I am not that used with mailing lists.
Actually, I have tried different solutions, including the flag you
proposed, I didn't kept it as I identified some side effect I thought
were linked to that option. However it was linked to some bad
structure declaration in some other part of the code...
Finally, after testing on some "sample" code it seems that it behaves
exactly like what I was asking for. Thanks a lot for your help !
--
ender
On Mon, Sep 29, 2008 at 7:49 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote:
> "andrew wiggin" <end3er@xxxxxxxxx> writes:
>
>> Thanks for your reply. I missed the * after the void as originally all
>> the types I use are tagged like u32 / s32 / u16 etc...
>>
>> So, my Target is ARM9(26EJ-S) in big endian mode. I used the t-arm-elf
>>>From gcc when compiling, I just removed the compilation for little
>> endian.
>> the structure I obtain is: {e1, {{e2[0].e1, e2[0].e2}, {X,X}},
>> {{e2[1].e1,e2[1].e2}, {X, X}}, e3}
>
> Please reply to the mailing list, not just to me. Thanks.
>
> For ARM, see the -mstructure-size-boundary option in the
> documentation.
>
> Ian
>
