The shootouts do not generally run under the default runcore, so these
are not ideal for a standard `make test`. For most of the tests, a
quick alternative for the slow runcore can be found(for some, the input
can be generated by fasta.pir). Both are ran under JIT, so it could be
a JIT problem. If it works under the slow runcore but not jit, it's a
jit issue(this is ignoring those weird bugs I remember that worked
under jit but not the slow runcore).
On May 3, 2007, at 7:35 PM, chromatic wrote:
On Thursday 03 May 2007 16:22:13 [EMAIL PROTECTED] wrote:
Sort the vtable functions list alphabetically and use a binary search
when
looking functions up by name. This gets us part way to some of the
speedup
we should see from the pdd15 implementation.
Time to run ../../parrot tcl.pbc t/cmd_append.t
Before: 10.3s
After: 9.3s
You may need to 'make clean'.
Even after 'make realclean', this breaks t/examples/shootout.t on
x86/Linux:
1..20
ok 1 - examples/shootout/ack.pir
ok 2 - examples/shootout/binarytrees.pir
not ok 3 - examples/shootout/fannkuch.pir
# Failed test (t/examples/shootout.t at line 102)
# got: 'Segmentation fault (core dumped)
# '
# expected: '1234567
# 2134567
# 2314567
# 3214567
# 3124567
# 1324567
# 2341567
# 3241567
# 3421567
# 4321567
# 4231567
# 2431567
# 3412567
# 4312567
# 4132567
# 1432567
# 1342567
# 3142567
# 4123567
# 1423567
# 1243567
# 2143567
# 2413567
# 4213567
# 2345167
# 3245167
# 3425167
# 4325167
# 4235167
# 2435167
# Pfannkuchen(7) = 16
# '
# './parrot -j
"/home/chromatic/dev/parrot/t/examples/shootout_3.pir"' failed
with exit code 139
ok 4 - examples/shootout/fasta.pir
ok 5 - examples/shootout/knucleotide.pir
not ok 6 - examples/shootout/mandelbrot.pir
# Failed test (t/examples/shootout.t at line 102)
# got: 'Segmentation fault (core dumped)
# '
# expected: 'P4
# 200 200
#
-- c
