Forgot to add: in many environments (at least SGI/MIPS, AIX Power/PPC,
HP-UX/HPPA) things are even more interesting -- one can in compile time
decide between different 32-bit modes and different 64-bit modes.
(E.g. in IRIX there are two of each.) I believe the new x86-ish
processors and Linux/gcc
Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> 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.)
Would break nicely ;)
leo
Jarkko Hietaniemi wrote:
Nick Glencross 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.
So what I'm confused about is why intsize=4 when you say the Parrot core
is 64 bit.
Nick Glencross wrote:
> Jarkko Hietaniemi wrote:
>
>
>>>Not true. We've done successful compiles before on Tru64. Maybe as of 0.0.6
>>>
> 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 th
Jay,
Jay Scherrer wrote:
> Attached is my make test output from my laptop running Fedora Core 3
> x86_64bit: makeTest.txt
> Is there any other way I can help?
>
Thanks for that Jay. What's happened is that in the last week a new test
has gone into CVS, but I haven't had access to systems besides a
Jarkko Hietaniemi wrote:
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
>
> 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-b
Attached is my make test output from my laptop running Fedora Core 3
x86_64bit: makeTest.txt
Is there any other way I can help?
Jay Scherrer
On Fri, 2005-04-01 at 11:24 -0500, MrJoltCola wrote:
> At 06:33 AM 4/1/2005, Nick Glencross wrote:
>
> >Having never had access to a Tru64 system, does tha
MrJoltCola wrote:
At 06:33 AM 4/1/2005, Nick Glencross wrote:
Having never had access to a Tru64 system, does that mean that parrot
is compiled 64 bit?
Two initial comments:
* This is a platform that we've not had a chance to test on, so I'm
grateful to see it tested on a new platform. It was
At 06:33 AM 4/1/2005, Nick Glencross wrote:
Having never had access to a Tru64 system, does that mean that parrot is
compiled 64 bit?
Two initial comments:
* This is a platform that we've not had a chance to test on, so I'm
grateful to see it tested on a new platform. It was hoped that it woul
Nick Glencross wrote:
Having never had access to a Tru64 system, does that mean that parrot
is compiled 64 bit?
Two initial comments:
* This is a platform that we've not had a chance to test on, so I'm
grateful to see it tested on a new platform. It was hoped that it
would work, but to stop t
Leopold Toetsch wrote:
Original Message
Subject: a warning and a failure for parrot in Tru64
Date: Thu, 31 Mar 2005 20:41:30 +0300
From: Jarkko Hietaniemi <[EMAIL PROTECTED]>
To: Leopold Toetsch <[EMAIL PROTECTED]>
cc: Warning: pylist.pmc, line 601: In this statement, the referen
Original Message
Subject: a warning and a failure for parrot in Tru64
Date: Thu, 31 Mar 2005 20:41:30 +0300
From: Jarkko Hietaniemi <[EMAIL PROTECTED]>
To: Leopold Toetsch <[EMAIL PROTECTED]>
cc: Warning: pylist.pmc, line 601: In this statement, the referenced
type of the pointer
13 matches
Mail list logo
