Leopold Toetsch wrote:
On Dec 14, 2005, at 12:52, Joshua Isom (via RT) wrote:
[ substr related PANIC ]
After a lengthy session with gdb and some added debug prints, I've now
tracked down and fixed the reason for the memory panic. The sweep code
tried to avoid freeing buffers, if there were
On Dec 14, 2005, at 12:52, Joshua Isom (via RT) wrote:
[ substr related PANIC ]
I've now a rather simple test case: a string reverse_inplace that shows
some parts of the problem.
(You might ulimit -v yourself to a few 100 Megs before running the
program)
.sub main :main
.local string
Leopold Toetsch wrote:
> We will need tr///, if we want that benchmark complete in reasonable time.
Better still, we could add some new opcodes, each of which performs one
entire shootout benchmark :-)
Regards,
Roger Browne
On Dec 14, 2005, at 18:08, Leopold Toetsch wrote:
... You should also avoid the extra $S0 copy and just work inside
'line' and substr in width chunks just for printing.
Oops. That would create the same problem but worse - 'line' aka 'seq'
would be reallocated.
leo
Joshua Isom (via RT) wrote:
For the reverse-compliment benchmark, I've gotten it working(albeit not
well), but with one major caveat. Since, to my knowledge, parrot has
no equivalent of perl's tr///,
We will need tr///, if we want that benchmark complete in reasonable time.
.. I implement
# New Ticket Created by Joshua Isom
# Please include the string: [perl #37940]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37940 >
For the reverse-compliment benchmark, I've gotten it working(albeit not
well), but with
Forgot the file.
revcomp.pir
Description: Binary data
