Re: Padding in gcc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 7/9/07, Rajat Jain <Rajat.Jain@xxxxxxxxxxxx> wrote:


>> Can we always rely on the fact that gcc will pad the following structure?
>> typedef struct {
>>     int descrp;      SYSCALL64_STRUCT_ATTR;
>>     (Automatic padding here?)
>>     long long pos;   SYSCALL64_STRUCT_ATTR;
>>     int mode;        SYSCALL64_STRUCT_ATTR;
>> } lseek64_t;
>> What is the correct way to make it portable? Explicitly added padding

>may be i am missing something but why is this not portable? And how
>does padding makes this portable?

Hi ... sorry I could not ask very well, what I wanted to. I have a piece of
code that ASSUMES that the above structure is padded (and I do not want to
change that code). So how can I make sure that this structure is always
padded (Is there any other way apart from adding explicit padding field?)

So like we have a "packed" gcc attribute, do we have a "padded" gcc
attribute or something like that (that ensures that gcc will always pad this
GCC will always pad it for best alignment depending on the
architecture. There is attribute to avoid this padding  though.
But padding is done by default depending on architecture for which you
compile your program.
So as long as cross compiliation process is correct, it should work i guess.

OTOH do you want to add just a fixed number of bytes irrespective of
the architecture?

[PS : psbl has blacklisted me ,please CC to newbies too, just in case]


play the game
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at

[Site Home]     [Audio]     [Hams]     [Kernel Newbies]     [Memory]     [Security]     [Netfilter]     [Bugtraq]     [Photo]     [Yosemite Photos]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linux Resources]     [Fedora Users]

  Powered by Linux