classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2nd attempt at Re: The right way(tm) of writing toString() (Was: Re:


From: David Lichteblau
Subject: Re: 2nd attempt at Re: The right way(tm) of writing toString() (Was: Re: [PATCH] Field position attribute handling)
Date: Sun, 30 Nov 2003 18:54:26 +0100
User-agent: Mutt/1.3.28i

Quoting Dalibor Topic (address@hidden):
> I doubt that it only helps with interpreters. I'd assume that it also 
> helps with kaffe's JIT, for example. But every little bit helps ;)

Fair enough.  I will have to learn about kaffe's JIT then.

> Basically, you want to have a JIT that rewrites
> 
>   sb.append("something");
>   sb.append("else");
> 
> into
> 
>   sb.append("something").append("else");

More precisely, a JIT that compiles both forms into machine code of
similar performance, where the difference is probably a load of `sb'
from memory for each method invocation.

(A sufficiently smart compiler might do what you are describing, but
that sounds a little unrealistic to me, too.)

> In any case, the question is: can we assume that VMs using GNU Classpath 
> have good JITs? I think the answer is 'No', despite the great 

Well, I guess that was my question.


Thanks,
David

Attachment: pgpI9vy90fzCm.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]