One possible solution could be the introduction of aliases for symbol names. So the symbol names could be reduced to an optimal length and names with up to 4K characters could be avoided. If there was made heavy use of STL and namespaces very long symbols names are the result.
There are other reasons why gcc generated libraries are pretty huge, see also some sizing experiments we've done on SRC624.
OpenOffice.org Version | Startup (first start after installation) | Memory footprint after start and late init |
---|
VmSize | VmRss | VmData | ||
OpenOffice627 | 65 sec | 104768Kb/49676KB/16360kb | ||