# New Ticket Created by The RT System itself
# Please include the string: [perl #19192]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=19192 >
I can build parrot fine on my FreeBSD box. I can re-run the tests fine with
/usr/local/bin/perl5.8.0 t/harness quick
All tests successful, 18 subtests skipped.
Files=42, Tests=581, 205 wallclock secs (65.07 cusr + 38.41 csys = 103.48 CPU)
However, if I try to test the JIT:
/usr/local/bin/perl5.8.0 t/harness -j quick
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/op/trans.t 2 512 18 2 11.11% 11 18
t/pmc/perlstring.t 1 256 8 1 12.50% 3
t/pmc/pmc.t 1 256 80 1 1.25% 36
18 subtests skipped.
Failed 3/42 test scripts, 92.86% okay. 4/581 subtests failed, 99.31% okay.
Details are:
t/op/trans..........NOK 11# Failed test (t/op/trans.t at line 251)
# got: 'ok 1
# not ok 2
# '
# expected: 'ok 1
# ok 2
# '
t/op/trans..........NOK 18# Failed test (t/op/trans.t at line 479)
# got: 'not ok 1
# not ok 2
# not ok 3
# not ok 4
# not ok 5
# not ok 6
# ok 7
# ok 8
# ok 9
# ok 10
# not ok 11
# not ok 12
# ok 13
# not ok 14
# not ok 15
# ok 16
# '
# expected: '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
# '
# Looks like you failed 2 tests of 18.
t/op/trans..........dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 11, 18
Failed 2/18 tests, 88.89% okay
t/pmc/perlstring....NOK 3# Failed test (t/pmc/perlstring.t at line 137)
# got: 'ok 1
# ok 2
# ok 3
# ok 4
# ok 5
# not ok 6
# '
# expected: 'ok 1
# ok 2
# ok 3
# ok 4
# ok 5
# ok 6
# '
t/pmc/perlstring....ok 8/8# Looks like you failed 1 tests of 8.
t/pmc/perlstring....dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 3
Failed 1/8 tests, 87.50% okay (less 1 skipped test: 6 okay, 75.00%)
t/pmc/pmc...........NOK 36# Failed test (t/pmc/pmc.t at line 585)
# got: 'ok 1
# ok 2
# ok 3
# 0.000000not ok 4
# ok 5
# ok 6
# ok 7
# ok 8
# 0.000000not ok 9
# ok 10
# ok 11
# ok 12
# '
# expected: 'ok 1
# ok 2
# ok 3
# ok 4
# ok 5
# ok 6
# ok 7
# ok 8
# ok 9
# ok 10
# ok 11
# ok 12
# '
t/pmc/pmc...........ok 80/80# Looks like you failed 1 tests of 80.
t/pmc/pmc...........dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 36
Failed 1/80 tests, 98.75% okay (less 2 skipped tests: 77 okay, 96.25%)
Unlike the previous JIT bug, this doesn't seem to be due to the JIT using
instructions that are absent on the K5. (Or at least it's not core dumping
with SIGILL)
CPU is:
CPU: AMD-K5(tm) Processor (100.23-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x514 Stepping = 4
Features=0x21bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE>
AMD Features=0x0
real memory = 16777216 (16384K bytes)
avail memory = 13422592 (13108K bytes)
Hmm. I'd not looked at that before. Maybe my sister was mistaken when she
gave it to me saying it was 133 Mhz. I'll have to get my money back. All �0. :-)
uname -a reports:
FreeBSD thinking-cap.moo 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Sat Jul 13 18:39:23 GMT
2002 [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/THINKINGCAP i386
The same JIT test passes 100% on another FreeBSD machine I have access to.
Although this isn't totally helpful, as that machine has a Citrix processor,
and it's more recent than my K5
Nicholas Clark
