|link-optimization in C firstname.lastname@example.org (S. Bochkarev) (1999-05-21)|
|Re: link-optimization in C email@example.com (Christopher Brian Colohan) (1999-05-22)|
|Re: link-optimization in C firstname.lastname@example.org (1999-05-22)|
|Re: link-optimization in C email@example.com (Jan Gray) (1999-05-22)|
|Re: link-optimization in C firstname.lastname@example.org (Bill A.) (1999-05-27)|
|Re: link-optimization in C email@example.com (Jeffrey A Law) (1999-05-27)|
|Re: link-optimization in C firstname.lastname@example.org (Bill Fahle) (1999-06-27)|
|From:||Jeffrey A Law <email@example.com>|
|Date:||27 May 1999 23:25:13 -0400|
> >Actually, CodeWarrior for Win32 (by default) and MS Visual C++ (when
> >used with the /Gy switch) both perform this procedure you mention --
> >we put each procedure in its own section, and the respective linkers
> >dead-strip out unused functions in the final executable.
> The Watcom C/C++ linker also removes dead code and can remove unused
> non-virtual and virtual functions by choice.
The GNU tools can do this on ELF platforms. Though the removal of
unused virtual functions isn't supported on all platforms (yet).
Return to the
Search the comp.compilers archives again.