Netbeans Beta and RC releases
<DIV><SPAN class=203500921-02082002><FONT face=Arial size=2>Can anyone tell me
if the binaries distributed for download that are posted as beta builds or
Release candidates</FONT></SPAN></DIV>
<DIV><SPAN class=203500921-02082002><FONT face=Arial size=2>are compiled with
optimizations turned on? Or are they instead compiled in debug
mode.</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2>Andrew
Chandler ;
Visionael Corporation</FONT></DIV>
<DIV><FONT face=Arial size=2>Manager DataCollection Group
<A
href="mailto:achandler@visionael.com">achandler@visionael.com</A></ FONT></DIV>
<DIV><FONT face=Arial size=2>410 Cambridge
Ave &nbs p; Tel:
650-470-8920x1535</FONT></DIV>
<DIV><FONT face=Arial size=2>Palo Alto, CA
94306 &n bsp; Fax:650-470-8921</FONT></DIV> ;
<DIV><FONT face=Arial
size=2> &nb sp; ;
<A href="http://www.visionael.com/">www.visionael.com</A></FONT>< ;/DIV>
<DIV> </DIV>
# 1
Andrew Chandler wrote:
> Can anyone tell me if the binaries distributed for download that are
> posted as beta builds or Release candidates
> are compiled with optimizations turned on?Or are they instead
> compiled in debug mode.
They are compiled with a default level of debug info (basic line number
tables so stack traces are meaningful). They do not have full debug info
(local variable tables etc.) as this would make the download enormous,
and is only useful for running NB itself through a debugger (for which
you should build from sources).
As for -O, no. It is pretty well useless for Java code, I guess. In
practice there are few compile-time optimizations that a Java compiler
can do safely, because of late linking, and javac does almost none.
HotSpot however does heavy dynamic optimization of frequently-run
bytecode, so there is not much need for help from the compiler.
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
# 2
Ok, I can accept that you may not feel it worth it for the overall
distributions, but
can you point me to the right way to modify the ant build.xml file to add
the -O parameter?I'm looking and may yet find it but help's also
appreciated.I kind of just want to do some empirical tests between with
and without.
--Original Message--
From: Jesse Glick [mailto:jesse.glick@sun.com]
Sent: Friday, August 02, 2002 2:34 PM
To: nbusers@netbeans.org
Subject: Re: Netbeans Beta and RC releases
Andrew Chandler wrote:
> Can anyone tell me if the binaries distributed for download that are
> posted as beta builds or Release candidates
> are compiled with optimizations turned on?Or are they instead
> compiled in debug mode.
They are compiled with a default level of debug info (basic line number
tables so stack traces are meaningful). They do not have full debug info
(local variable tables etc.) as this would make the download enormous,
and is only useful for running NB itself through a debugger (for which
you should build from sources).
As for -O, no. It is pretty well useless for Java code, I guess. In
practice there are few compile-time optimizations that a Java compiler
can do safely, because of late linking, and javac does almost none.
HotSpot however does heavy dynamic optimization of frequently-run
bytecode, so there is not much need for help from the compiler.
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
# 3
Ok, I think I figured it out - I added an optimize="true" to the javac
directive
in the NBBuild directory.My only concern now is does this cover the
entire build or are there sub-builds in each project directory as well.
Thanks anyhow for the help.
--Original Message--
From: Andrew Chandler [mailto:andy@riftware.com]
Sent: Friday, August 02, 2002 3:23 PM
To: nbusers@netbeans.org
Subject: RE: Netbeans Beta and RC releases
Ok, I can accept that you may not feel it worth it for the overall
distributions, but
can you point me to the right way to modify the ant build.xml file to add
the -O parameter?I'm looking and may yet find it but help's also
appreciated.I kind of just want to do some empirical tests between with
and without.
--Original Message--
From: Jesse Glick [mailto:jesse.glick@sun.com]
Sent: Friday, August 02, 2002 2:34 PM
To: nbusers@netbeans.org
Subject: Re: [nbusers] Netbeans Beta and RC releases
Andrew Chandler wrote:
> Can anyone tell me if the binaries distributed for download that are
> posted as beta builds or Release candidates
> are compiled with optimizations turned on?Or are they instead
> compiled in debug mode.
They are compiled with a default level of debug info (basic line number
tables so stack traces are meaningful). They do not have full debug info
(local variable tables etc.) as this would make the download enormous,
and is only useful for running NB itself through a debugger (for which
you should build from sources).
As for -O, no. It is pretty well useless for Java code, I guess. In
practice there are few compile-time optimizations that a Java compiler
can do safely, because of late linking, and javac does almost none.
HotSpot however does heavy dynamic optimization of frequently-run
bytecode, so there is not much need for help from the compiler.
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
# 4
Andrew Chandler wrote:
> Ok, I think I figured it out - I added an optimize="true" to the javac
> directive
> in the NBBuild directory.My only concern now is does this cover the
> entire build or are there sub-builds in each project directory as well.
That only covers a handful of classes used only at build time. You would
need to edit every build.xml in each project subdir. For deprecations
and debug info, you can set these via an Ant property, since there are
known reasons to turn these on globally in some cases. For optimization,
I don't think anyone has ever bothered. Maybe you can get some speedup,
it would be interesting to find out.
-Jesse
--
Jesse Glick <mailto:jesse.glick@sun.com> x22801
NetBeans, Open APIs <http://www.netbeans.org/>
