On Monday 06 April 2009 16:43:48 Parrot wrote:
> Thanks for the very thorough presentation. But, as reported on #parrot, I
> could not reproduce the test failures in Linux/i386:
I can, but check this out.
> {{{
> $ ./parrot -Rjit t/op/trans_13.pasm
> ok 1
> ok 2
> ok 3
> ok 4
> ok 5
> ok 6
> ok 7
> ok 8
> ok 9
> ok 10
> ok 11
> ok 12
> ok 13
> ok 14
> ok 15
> ok 16
>
> $ cat myconfig
> Summary of my parrot 1.0.0 (r37932) configuration:
> configdate='Mon Apr 6 22:52:56 2009 GMT'
> Platform:
> osname=linux, archname=i686-linux
> jitcapable=1, jitarchname=i386-linux,
> jitosname=LINUX, jitcpuarch=i386
> execcapable=1
> perl=/usr/local/bin/perl
Summary of my parrot 1.0.0 (r0) configuration:
configdate='Thu Mar 26 20:50:57 2009 GMT'
Platform:
osname=linux, archname=i486-linux-gnu-thread-multi
jitcapable=1, jitarchname=i386-linux,
jitosname=LINUX, jitcpuarch=i386
execcapable=1
perl=/usr/bin/perl
I wonder if archname=i486-linux-gnu-thread-multi is the culprit?
-- c
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
