Thanks for the responses.
I'll not bother with -O then!
I've given the profiler a go and I'm managing to understand parts of it. I've not
looked at the sun site but if there is comprehensive info on the site then I'll look
there as this probably isn't Linux specific any more.
By the way cpu:s
I think the documentation for Sun's "javac" says
that "-O" is a NOP.
In theory (and in practice with some other compilers :-)
there's a fair degree of scope for optimizing intermediate
code. Not just dead code elimination, but reorganizing
basic blocks, eliminating temporaries, and so on. (The
On Thu, Nov 02, 2000 at 11:29:00AM +, KIRKBRIDE Rob wrote:
> Thanks a lot for the info yes it was the JDK optimizer I was interested in, but I
>may give the profiler a go as I've had much success on other projects (not involving
>java)
> I was thinking of gcc in that gcc is known to produce
KIRKBRIDE Rob wrote:
>
> Thanks a lot for the info yes it was the JDK optimizer I was interested in
Oh, you mean "javac -O"? I'm afraid that's not very useful speed-wise. I
have never noticed a noticeable speed difference between -O and not -O
with the Blackdown JDK, but on the other hand I have
Thanks a lot for the info yes it was the JDK optimizer I was interested in, but I may
give the profiler a go as I've had much success on other projects (not involving java)
I was thinking of gcc in that gcc is known to produce very non-optimal code unless
optimisation is performed, I wondered wh
Has anyone got any feelings/figures for the usefulness of code optimisation using the
Blackdown 1.2.2 JDK?
I may do some experimentation but I wondered if anyone had done any analysis on
whether it makes much difference. Obviously it will depend on the code, but do people
use it as a matter of
