On 7/9/07, Rajat Jain <Rajat.Jain@xxxxxxxxxxxx> wrote:
Hi,
Perhaps a little offtopic but no harm in trying ...
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?
Please enlighten me.
Thanks
Thanks,
Rajat
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
