Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 16, 2003 at 05:40:30PM +0200, Leopold Toetsch wrote:
>> As JIT code is unrolled, it IMHO can only call the function core (or CGP
>> again) for loaded opcodes.
> As is this would mean that the JIT can't JIT any opcodes that are brought
> in b
On Thu, 16 Oct 2003, Nicholas Clark wrote:
> On Thu, Oct 16, 2003 at 05:40:30PM +0200, Leopold Toetsch wrote:
>
> > As JIT code is unrolled, it IMHO can only call the function core (or CGP
> > again) for loaded opcodes.
>
> As is this would mean that the JIT can't JIT any opcodes that are brought
On Thu, Oct 16, 2003 at 05:40:30PM +0200, Leopold Toetsch wrote:
> As JIT code is unrolled, it IMHO can only call the function core (or CGP
> again) for loaded opcodes.
As is this would mean that the JIT can't JIT any opcodes that are brought
in by dynamically loaded classes, it would be pain fo
Now all run cores[2] are able to execute dynoplibs/test.pasm [1].
This is currently done for all cores except the function (slow) core by
running the wrapper__ opcode, which calls the real function in the
parrot function core.
Cores with an address table for function dispatch (CGoto, CGP) get a
