On Jun 7, 2007, at 3:19 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #43145]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43145 >
In config/auto/jit.pm there is the todo item (well, it *could* be a
todo item):
# XXX disable all but i386, ppc
and a note that "all others are seriously b0rked".
One would guess that the intention of the todo item here is to un-b0rk
the other platforms. If this is not the case, and the XXX in the code
is merely there as a marker, then it should be changed to a different
marker and/or the comment altered appropriately.
If the code for that platform won't even compile anymore, then enabling
jit on these platforms will break the compile. If you pass
--jitcapable to Configure.pl it will override that hash so that the jit
will be included. To "untodo" it at the moment, aside from fixing
them(which would require someone with that arch to update it), would be
to delete the directory entirely, which is probably not the best
option.
To me, the more annoying issue is the error message you get if you pass
-j to parrot without jit, "Error: PARROT_JIT_FLAG is set, but
interpreter is not JIT_CAPABLE!"
