As promised in parrotsketch, I've opened tickets for the remaining
segfaults in the partcl spec test suite. Some of these will resolve
more than one test, even though I've only listed one tcl test in the
trac ticket.
TT's 961, 962, 963, 964, 965, 966.
Thanks in advance.
--
Will "Coke" Coleda
__
https://trac.parrot.org/parrot/browser/branches
The following branches have had no activity in >= 2months:
isafast/
nsentry/
pmc_i_ops/
pmc_pct/
remove_pic/
strings/
vc9/
___
http://lists.parrot.org/mailman/listinfo/parrot-dev
In response to our discussion today in #ps, I have started drafting
some plans for implementing a proper JIT for Parrot. I have tried to
show several options for each step, each with pros and cons:
https://trac.parrot.org/parrot/wiki/JITRewrite
We need more input on this topic from everybody. We
Allison Randal wrote:
This branch is a part-way step to a larger goal, so this is a sanity
check that these changes are headed toward the final goal.
Ok. I'm done with scope of current branch. Only one thing to do _before_
merge is fixing JIT failure (breaking point can be easily spotted by
m
