[EMAIL PROTECTED] wrote on 06/05/2005 10:48:29 PM:
- The machine code concatinating technique consumes much memory.
In my experience, generated machine code is about 10 times larger
than the original instructions in Java bytecode.
In the paper, the authors have not mentioned memory
Hi Dave,
From: David P Grove [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote on 06/05/2005 10:48:29 PM:
- The machine code concatinating technique consumes much memory.
In my experience, generated machine code is about 10 times larger
than the original instructions in Java bytecode.
Hi,
On 6/6/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi Dave,
From: David P Grove [EMAIL PROTECTED]
One thing to
note is that a threaded interpreter would see something like a 2-4x
expansion over normal bytecodes when it converts from bytecodes to its
internal form (arrays of
Hi Rob,
From: Robert Lougher [EMAIL PROTECTED]
Date: Mon, 6 Jun 2005 14:58:45 +0100
One thing to
note is that a threaded interpreter would see something like a 2-4x
expansion over normal bytecodes when it converts from bytecodes to its
internal form (arrays of function pointers).
Hi Steve and all,
| The approach of using C Compiler generated code rather than writing a
| full compiler appeals to me:
| http://www.csc.uvic.ca/~csc586a/papers/ertlgregg04.pdf
From: Steve Blackburn [EMAIL PROTECTED]
Date: Tue, 24 May 2005 21:08:05 +1000
They automatically build themselves
[EMAIL PROTECTED] wrote:
They automatically build themselves
simple JIT backends (by extracting fragments produced by the ahead of
time compiler). This sounds like a great way to achieve portability
while achiving better performance than a conventional interpreter.
I guess it's a bit
Other interesting things that can be achieved are some sorts of high
performance tunning aspects, which are very interesting, and using gcc
power might be more interesting than redoing it from scratch, either, at
the begining of current project, or maybe forever.
An adequate bundle of gcc and
optimizing" plugin, which does not need to tackle with anything but
code generation itself - if this is really possible)
-Original Message-
From: Ariel Sabiguero Yawelak [mailto:[EMAIL PROTECTED]
Sent: Monday, May 23, 2005 5:06 PM
To: harmony-dev@incubator.apache.org
From: Steve Blackburn [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
The approach of using C Compiler generated code rather than writing a
full compiler appeals to me:
http://www.csc.uvic.ca/~csc586a/papers/ertlgregg04.pdf
I am curious on how well the approach performs compared to
[EMAIL PROTECTED] wrote:
The approach of using C Compiler generated code rather than writing a
full compiler appeals to me:
http://www.csc.uvic.ca/~csc586a/papers/ertlgregg04.pdf
I am curious on how well the approach performs compared to existing JITs.
I'm admittedly biased, but the approach
Archie Cobbs wrote:
[EMAIL PROTECTED] wrote:
The approach of using C Compiler generated code rather than writing a
full compiler appeals to me:
http://www.csc.uvic.ca/~csc586a/papers/ertlgregg04.pdf
I am curious on how well the approach performs compared to existing
JITs.
I'm admittedly
11 matches
Mail list logo
