home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.g++.help
- Path: sparky!uunet!ascent!eb
- From: eb@ascent.com (Ed Barton)
- Subject: g++ executable size
- Message-ID: <EB.92Jul29092745@ascent.ascent.com>
- Date: 29 Jul 92 09:27:45
- Organization: Ascent Technology, Inc., Cambridge Massachusetts
- Lines: 13
-
-
- As has often been noted, g++ 2.2.2 on the IBM RS/6000 produces
- enormous executables. This appears to result from the generation of
- multiple local copies of various method functions. Are there any
- tricks for reducing this effect, such as by turning on some linker
- flag in the second link phase only that would allow the linker to
- garbage-collect most of the local copies? Are there any undocumented
- flags that allow greater control over the generation of these possibly
- duplicated copies, as is possible in many PC products?
-
-
-
-
-