Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2

[Toon Moene]

Jim Wilson wrote:

> On a completely different tack, another way to reduce the impact of
> debug info is to not put it in the final executable, and modify the
> debugger to read debug info from the object files.  Sun has done this
> for a long time with stabs.  There is some work at Red Hat being done to
> try do the same thing for DWARF2.  This makes linking faster, and gives
> smaller executables with no debug info at all, but makes debugging a bit
> slower.

Well, that only works if you keep the objects :-)

Our mode of operation is:

To compile:

1. Compile Fortran code.
2. Put object into library.
3. Delete object.

To link:

4. Compile the Fortran "main" program:

       call <main-sub>
       end

5. Link the object resulting from this with the relevant
    libraries.

How would your scheme work in this case ?

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://gcc-g95.sourceforge.net/ (under construction)