Jarkko Hietaniemi wrote:
Ok, so intsize=4, which is why my md5 test tried to run. I'd be really grateful if some could run my instrumented MD5.imc from a previous post on this platform.Not true. We've done successful compiles before on Tru64. Maybe as of 0.0.6
True, not true :-) I do manual test compiles in Tru64 once in a while. Once the packfile portability problems were solved back when, the Parrot core at least has been pretty good regarding 64-bitness.
Tru64 is 64-bit little-endian, with longsize=ptrsize=8 intsize=4 (shortsize=2).
P.S. (I wish I still had Cray 90 access, the unusual-but-legal
longsize=ptrsize=intsize=shortsize=8 nicely shook bugs to the bright
light of day in Perl 5.)
So what I'm confused about is why intsize=4 when you say the Parrot core is 64 bit. Isn't one of the points of a 64-bit processor to have larger ints (often accompanied by larger address space)? So if ints are just 4 bytes, what would trip things up on Tru64?
There are a few reasons why I'm keen to get this resolved. 1) My assumption that intsize!=4 for 64-bit processors is broken, which is why the test is seen to fail. 2) I would like the library to work on all platforms. 3) I'm curious to know why it doesn't work, as it was expected to work on different endianess and word size. 4) the md5 library has been, and hopefully will continue to be, a good way to shake problems out of the parrot core.
Thanks all,
Nick
