Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!gatech!rutgers!ucsd!nprdc!stanonik
From: stanonik@nprdc.navy.mil (Ron Stanonik)
Newsgroups: comp.unix.programmer
Subject: Re: struct 32 bit aligned and padded
Message-ID: <14236@arctic.nprdc.navy.mil>
Date: 19 Apr 91 17:21:06 GMT
References: <14082@arctic.nprdc.navy.mil> <4101@risky.Convergent.COM>
Sender: news@nprdc.navy.mil
Reply-To: stanonik@nprdc.navy.mil (Ron Stanonik)
Organization: Navy Personnel R&D Center, San Diego
Lines: 15

Alignment I can understand, but padding just seems like the
compiler writers got lazy.  It also meant that sizeof(struct packet)
wasn't the packet size, when the packet didn't end on a 32 bit boundary;
ie, we had to count up the bytes by hand to figure packet sizes.
We looked in vain for any cc flags that might disable padding,
but, as you said, we'd be wary of using such a flag for fear of
fouling up some sysV.3.2 include that expected the padding.
Did the 3b2 folks really use this compiler to compile the kernel;
ie, they didn't encounter any problems with this padding?

Thanks,

Ron Stanonik
stanonik@nprdc.navy.mil
ucsd!nprdc!stanonik