Tom Tromey writes:
> > "Matthew" == Matthew Fortune writes:
>
> Matthew> Sorry for the long delay...
>
> No problem.
>
> >> This is ok.
> >> Could you check? I think a -m32 build ought to show it. Maybe your
> >> x86-64 build already did
> "Matthew" == Matthew Fortune writes:
Matthew> Sorry for the long delay...
No problem.
>> This is ok.
>> Could you check? I think a -m32 build ought to show it. Maybe your
>> x86-64 build already did this?
Matthew> Still OK to commit?
Yes, thanks.
Tom
Tom Tromey writes:
> > "Matthew" == Matthew Fortune writes:
>
> Matthew> I'm not sure this will matter if the only arch is x86 as
> Matthew> ffi_arg will be 32-bit anyway there.
>
> Aha, right. Thanks for looking.
>
> Matthew> There would need
> "Matthew" == Matthew Fortune writes:
Matthew> I'm not sure this will matter if the only arch is x86 as
Matthew> ffi_arg will be 32-bit anyway there.
Aha, right. Thanks for looking.
Matthew> There would need to be a
Matthew> 64bit arch using the raw api. I
Tom Tromey writes:
> > "Matthew" == Matthew Fortune writes:
> Matthew> I've identified a latent bug in the java interpreter that affects
> MIPS
> Matthew> n32 and n64 ABIs both little and big endian and, I presume, any
> 64-bit
> Matthew> big
> "Matthew" == Matthew Fortune writes:
Matthew> I've identified a latent bug in the java interpreter that affects MIPS
Matthew> n32 and n64 ABIs both little and big endian and, I presume, any 64-bit
Matthew> big endian target with int as 32-bit.
[...]
Matthew>
> "Matthew" == Matthew Fortune writes:
Matthew> I've identified a latent bug in the java interpreter that affects MIPS
Matthew> n32 and n64 ABIs both little and big endian and, I presume, any 64-bit
Matthew> big endian target with int as 32-bit.
Thanks.
Matthew>