On Thu, 21 Dec 2006, Roland Mainz wrote:
Hi!
----
Is there any reason that the Sun Studio compiler still gets called with
-xO[1-5]/-O (=optimizer enabled) when "bldenv" was called with the debug
switch ("-d") ? Sometimes this makes debugging (or core dump analysis)
harder then neccesary... ;-(
Exactly when ? Can you give an example ?
We're compiling only with -xO3 to make sure the framepointers stay in;
using this level also disables cross-function optimizations or automatic
inlining / elimination - so most of the "heavy" optimizations that really
change the code beyond recognition aren't done. You may loose unused
static variables, but that's about the only "maiming effect" I can think
of ?
My experience with the code generators, particularly on x86, is such that
the assembly code actually becomes quite unreadable when optimizaton is
disabled due to all the unnecessary loads/stores.
Bye,
FrankH.
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
