While this *may* be somewhat OT for this list, it might not... :)
I just "switched" (we'll see) to vs 2005 over the weekend, and the
first thing I recompiled was SciTE! I was shocked to find the exe
size go from 458 KB -> 541 KB. Sigh.
Since I think Neil has seen this changeover already, perhaps he will
have some comments?
For me, *every* [MS] compiler upgrade in the past has seen REDUCTIONS
in code size as the code generation has gotten smarter (v4 > v5 > v6 >
vs2003 < vs2005). Grrr. This is with the same options (primarily
Lua, static linking, smallest code size and limited inlining... and
[formerly] PII/PIII code generation).
The too biggest obvious "official" changes are the new "safe"
libraries, which of course are larger - not unreasonable. A trivial
app which uses printf and atoi went from 28.5 KB to 47 KB - again,
statically linked. So we get an idea that using some of the most
common portions of the CRT will add an extra ~20 KB.
BUT an 83 KB increase on a 458 KB app???
The other change (relating to code generation/size) is that the
intended target architecture model can no longer be specified... this
may be particularly unfortunate, since my own timing tests on my Core
2 Duo were showing [as expected] that the older PII/PIII model was a
better match performance-wise than the P4/Athlon models.
I now have no idea what they are assuming is the "ideal"
one-size-fits-all arch, but given the timing of vs 2005's development
and release, I bet it's heavily P4-slanted - as that appeared to be
the dominant architecture in that time frame.
So much for this rant - does anyone else have comments on what can be
done (if anything) to get code sizes back down? Have I missed a magic
option that says "remove added bloat"? ;)
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
