At 5:52 PM +0200 4/13/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
At 4:26 PM +0200 4/13/04, Leopold Toetsch wrote:
or tools/dev as it isn't quite required for building parrot?
That works too--I don't really care as long as it's in. :) If you
want to move it go ahead, that
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 4:26 PM +0200 4/13/04, Leopold Toetsch wrote:
>>
>>or tools/dev as it isn't quite required for building parrot?
> That works too--I don't really care as long as it's in. :) If you
> want to move it go ahead, that's fine. (I think I may take a shot at
>
At 4:26 PM +0200 4/13/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
This looks quite nice and works as a standalone utility, so I'll put
it in the repository as build_tools/list_unjitted.pl.
or tools/dev as it isn't quite required for building parrot?
That works too--I don't
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> This looks quite nice and works as a standalone utility, so I'll put
> it in the repository as build_tools/list_unjitted.pl.
or tools/dev as it isn't quite required for building parrot?
leo
At 2:54 PM +0200 4/8/04, Stefan Lidman wrote:
>Here's something for someone who wants to dig in a bit and needs a
place to start.
Many, but by no means all, of the ops are JITted right now. There's
code to mess about with the JITting in jit2h.pl. What would be nice
is if there was a way to get a
>Here's something for someone who wants to dig in a bit and needs a
>place to start.
>
>Many, but by no means all, of the ops are JITted right now. There's
>code to mess about with the JITting in jit2h.pl. What would be nice
>is if there was a way to get a list of the ops that are *not* JITted,
