On 27 Jan 2003, Juergen Boemmels wrote:
> Nicholas Clark <[EMAIL PROTECTED]> writes:
> > > struct Chunk {
> > > opcode_t type;
> > > opcode_t version;
> > > opcode_t size;
> > > void data[];
> > > };
> > I agree with the "roughly" bit, but I'd suggest ensuring that you put
> > in enough bits to get data[] 64 bit aligned. Mainly because at least 1
> > architecture exists that has no 32 bit types (Crays I know about; others
> > may exist. I can't remember if perl 5.8 passes 100% of tests on Crays.
> > We certainly tried)
>
> opcode_t will be 64 bit on this architectures.
For native bytecode, yes. However, consider a bytecode file generated on
a machine with a 32-bit opcode_t that is now being read on a machine with
a 64-bit opcode_t. In that case, it would be helpful if the data were
aligned on a 64-bit boundary.
--
Andy Dougherty [EMAIL PROTECTED]
