Joe Buck wrote:
Let's be careful to distinguish code optimizations, and optimizations that avoid the generation of unnecessary debug information. It used to be that every once in a while, in response to a bug report, a GCC developer would make a change that doubles or triples the size of a debug executable. For C++, where the size can already be massive, this can be a killer.
Well makes sense, but of course the key word is "unnecessary" in the above para, that's what makes this not quite so straightforward :-)
