🚀 go-pugleaf

maverick@halcyon.com (Thomas M. J. Fruchterman) writes:
>  I have been developing a large class library in g++. I am finding that 
>code files (*.o) for deeply nested classes are growing very large even
>though I am only overriding one or two methods in the derived class.
>  Devived classes are on the order of 10 levels deep 
>  single inheritance only
>  approximately 100 -200 methods in the virtual function table
>  total instance data approximately 100 bytes
>  size of .o file without debugging code - approximately 50K. 
>
>  I need to reduce that 50k number to something reasonable. Does anyone
>have experience with what causes this bloat and how to deal with it

Use #pragma interface and #pragma implementation.  See the gcc
manual for details.  Right now, you're probably getting many copies
of virtual function tables and "inlined" functions that can't be
inlined (if you don't say -O, then no "inlined" functions are inlined).
The pragmas cause only one copy to be generated.


-- 
-- Joe Buck	jbuck@synopsys.com
Posting from but not speaking for Synopsys, Inc.
Formerly jbuck@<various-hosts>.eecs.berkeley.edu