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
I used g++ instead of gcc now and it seems the error is fixed.
thanks for your help. l learned a lot about library files now.
Cheers,
Kason
Joi Ellis wrote:
> On Tue, 31 Oct 2000, kason wong wrote:
>
> > Hi,
> >
> > I guess I know what's the really problem is.
> >
> > I think I should make my p
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
