> >PS: I've tried one day the 2*64 definition on a Sparc (ie. with 64 bit
> >alignment). It didn't work because of some details, for instance the
> >route structure (pointer + sockaddr) or IPv6 over ATM (32 bit difference
> >in alignment between unicast and multicast). I can't see a good reason
> >to add a new source of problems...
> for the latter case, you need __attribute__((__packed__)) (gcc-ism)
> for header declaration. to control structure packing.
>=> don't joke with my stomach! Just put the fields in the best order.
for packet format on the wire, you really need to control the alignment
of structure members explicitly. you cannot just rely upon the
compiler padding (or your code will not be future-proven).
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
