Unusually large data segments in executables.

Joe Buck jbuck@synopsys.com
Wed Jan 14 09:28:00 GMT 1998


> Thanks to all who replied to this and yes the answer was to use
> -fno-exceptions which causes the executable to end up smaller than the one
> produced by g++ 2.7.2.3. I had no idea how much extra code exception
> handling support produced.. blearg!

Yes, the bloat is worst on the x86 architecture; folks are working on
improvements.  The good news is that most of the extra stuff gets put
in its own section, which will never be paged into memory unless an
exception is actually thrown (so you pay a disk space cost for exceptions
but not nearly as much of a RAM cost).



More information about the Gcc mailing list