Hi,
>>
>> 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 fields?
>> 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 fields?
>may be i am missing something but why is this not
portable? And how
>does padding makes this portable?
>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 structure.).
Thanks,
Rajat
