On Thu, Oct 10, 2002 at 06:52:25PM +0000, Andy Dougherty wrote: > # New Ticket Created by Andy Dougherty > # Please include the string: [perl #17844] > # in the subject line of all future correspondence about this issue. > # <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17844 > > > > The combination of 64-bit INTVAL and 32-bit pointers doesn't work with the > Sparc jit. > > diff -r -u parrot-orig/config/auto/jit.pl parrot-andy/config/auto/jit.pl > --- parrot-orig/config/auto/jit.pl Thu Aug 8 23:18:04 2002 > +++ parrot-andy/config/auto/jit.pl Thu Oct 10 14:02:14 2002 > @@ -62,6 +62,10 @@ > > if (-e "jit/$cpuarch/core.jit") { > $jitcapable = 1; > + if ($cpuarch =~ /sun4|sparc64/ && > + Configure::Data->get('intvalsize') > Configure::Data->get('ptrsize')) { > + $jitcapable = 0; > + } > }
Whilst this patch is not wrong, it's curing the symptom rather than the case. The x86 JIT doesn't work very well with 64 bit INTVAL either (fails stuff then seems to lock up in a busy CPU loop in integer.t 35/37) Really we ought to be naming our JITs based on (something like) perl5 archnames - ie CPU, INTVAL size, NUMVAL size, pointer size, and possibly other fundamental things if they exist. Nicholas Clark