So far, the default configuration is not using BLITZ in release mode. There are two reasons for this:
a) MSC could not handle it (results in internal compiler error, probably due to .obj files getting too big)
b) There was a hope that not using BLITZ in release mode can improve the size of resulting binary
That said, with CLANG the first concern is irrelevant, works just fine in Win32. So maybe we should have BLITZ active by default for at least CLANG.
I have put this theory to test with TheIDE (in Win32):
Non BLITZ (using precompiled headers): size: 19003904, built in 5:00
BLITZ: size: 19454976, built in 1:39
So based on this, definitely worth it. That small difference in size can be attributed to additional speed optimizations (perhaps something more got inlined in BLITZ mode).
What about your projects? Is going BLITZ in release by default a good idea?
Members
Pages
Help
Register
Login
Home
