This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Size of binaries.
- From: Jean-Pierre Radley <jpr at jpr dot com>
- To: hylafax-users at hylafax dot org
- Cc: GCC Developers <gcc at gcc dot gnu dot org>
- Date: Fri, 2 Aug 2002 15:50:39 -0400
- Subject: Size of binaries.
Back in June, using whatever was the lastest experimental version of gcc
(I refresh it every week or so here), I compiled hylafax-4.1.2 on
OpenServer 5.0.6.
Today, using "gcc version 3.2 20020727 (experimental)", I compiled
hylafax-4.1.3.
The same options were used (-O -g).
The Hylafax code has relatively few changes between 4.1.2 and 4.1.3,
but the binaries are vastly larger.
For example:
-r-xr-xr-x 1 root sys 647220 Jun 10 15:43 /u/sbin/faxgetty.old
-rwxr-xr-x 1 root sys 2226824 Aug 2 15:01 /u/sbin/faxgetty
The 'file' command reports:
/u/sbin/faxgetty: ELF 32-bit LSB executable 80386, dynamically linked, stripped, debug
/u/sbin/faxgetty.old: ELF 32-bit LSB executable 80386, dynamically linked, stripped, debug
What might be causing this increase in binary size of about 350% (I see
for all of Hylafax's binaries)?
I tried recompiling smail and tcsh, which were both last compiled almost
a year ago. The smail binary came out trivially different, while the
tcsh binary was in fact a bit smaller.
The Hylafax code is mostly in C++, and I have really no other C++ source
code to play with just now. I did see the following warning for just
about every *.c++ file:
/usr/local/include/c++/3.2/backward/backward_warning.h:32:2:
warning: #warning This file includes at least one deprecated
or antiquated header. Please consider using one of the 32
headers found in section 17.4.1.2 of the C++ standard. Examples
include substituting the <X> header for the <X.h> header for
C++ includes, or <sstream> instead of the deprecated header
<strstream.h>. To disable this warning use -Wno-deprecated.
--
JP