Lib change leads to larger executables

[Frits van Bommel]

kris wrote:
> Isn't there some way to isolate the typeinfo such that only a segment is 
> linked, rather than the entire "hosting" module (the one that just 
> happened to be found first in the lib) ?

The obvious solution would be to always generate typeinfo even if it can 
be determined imported modules will already supply it. The current 
approach seems to confuse the linker, causing it to link in unrelated 
objects that happen to supply the symbol even though the compiler 
"meant" for another object file to supply it.

Yes, that will "bloat" object files, but the current approach apparently 
bloats applications. Care to guess which are distributed most often? ;)