Re: parrot compilation failure in Tru64

[Jarkko Hietaniemi]

On Sat, Sep 15, 2001 at 06:33:18PM +0100, Simon Cozens wrote:
> On Sat, Sep 15, 2001 at 06:32:57PM +0100, Philip Kendall wrote:
> > I posted a couple of bodge fixes from this, but I haven't done much in
> > the past couple of days... do we want to use a 32 bit type for reading
> > in bytecode or convert the 32 bit on-disc format into a 64 bit format in
> > memory before reading it on a platform with 64 bit IVs?
> 
> We also need to think about endianness. Urgh.
> 
> This is something I ought to seek consensus on. (And possibly a ruling from
> Dan.)
> 
> Do we *expect* Parrot bytecode to be portable? My gut reaction would be to

Never mind 'portable' for now, currently it's not even *working* on
64-bit platforms....

> say no, but I can see the arguments either way.
> 
> Simon

-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen