Philippe Lhoste wrote:
Robert Roessler wrote:
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).
[...]
BUT an 83 KB increase on a 458 KB app???
Note that in VC++6 project files, I always add a /opt:nowin98 option to
the linker.
It used to reduce the size of the created exe, at the cost of more work
at load time (IIRC): by default, the compiler padded the generated exe
with zeroes to make segments aligned on pages, still IIRC.
I wonder if this more or less hidden option is still here (and
effective) in VC2005...
You will be pleased to know it is still there ("hidden" under linker
optimizations in the IDE) - I don't leave home without it! :)
As for any extra work at load time, all the writeups say that this was
*only* an issue with Win98 - anything newer is not affected negatively
by packing everything down to smaller (512 bytes?) boundaries (which
makes one wonder why this has not become the default).
As for executable size, perhaps every new generation needs to learn
again that unchecked bloat benefits no one but the disk drive and
memory manufacturers. :)
There are usually ways to make small[er] executables - ATL/WTL at
least still have the option of minimizing the use of the CRT. It is
too bad that now one will have to screw around a lot to get smaller
files (when this matters, anyway)... vs 2003 had finally gotten its
library factored/segmented so that you didn't really need to. :(
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
