Daniel Grunblatt wrote:
Don't implement any print op yet, if I didn't understood wrong they are
going to be updated to use the IO system.
ok, I draw back them then.
but I found another use for the emit_call_abs() function to implement some
string stuff in JIT. as I already said, the speed
On Fri, 24 May 2002, Aldo Calpini wrote:
but I found another use for the emit_call_abs() function to implement some
string stuff in JIT. as I already said, the speed increase isn't at all
dramatic, but OTOH I have no idea how to do complicate stuff like allocating
memory natively in asm.
hello people,
I've implemented some print opcodes in JIT (for i386), but I would
like to know your opinion about these before submitting a patch.
in reality, there isn't a big performance boost, because I'm just
calling printf as the C opcode does. it just saves some
push/pop/call/ret
On Thu, 23 May 2002, Aldo Calpini wrote:
hello people,
I've implemented some print opcodes in JIT (for i386), but I would
like to know your opinion about these before submitting a patch.
in reality, there isn't a big performance boost, because I'm just
calling printf as the C opcode
Methamphetamine/Speed is probably unhealthy for parrots.
On 4/24/02 7:32 AM, Nicholas Clark [EMAIL PROTECTED] wrote:
On Wed, Apr 24, 2002 at 12:26:57PM +0100, Nicholas Clark wrote:
Jarkko mailed this URL to p5p:
http://developer.kde.org/~sewardj/
I'd not twigged, but the author
In message [EMAIL PROTECTED]
Nicholas Clark [EMAIL PROTECTED] wrote:
Jarkko mailed this URL to p5p:
http://developer.kde.org/~sewardj/
It describes a free (GPL) memory leak checker for x86 Linux
1: This may be of use for parrot hackers
Which is why I mentioned it a week
