This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Large a.out files
- To: egcs-bugs at egcs dot cygnus dot com
- Subject: Large a.out files
- From: Paul Ezust <ezust at cartan dot cas dot suffolk dot edu>
- Date: Tue, 23 Nov 1999 23:47:24 -0500 (EST)
Ever since our systems programmer upgraded to an Aug1999 version
of g++/egcs
{Reading specs from
/usr/local/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95.1/specs
gcc version 2.95.1 19990816 (release)}
we have been seeing *HUGE* a.out files.
For example, a recent homework that I assigned in my OOP course
produced:
arcadia:/usr/clas1/staff/ezust/C331/Hw9> ls -l a.out
-rwx------ 1 ezust users 1237992 Nov 23 15:54 a.out*
This is consistent with the sizes that I have been seeing all semester.
I then took the same code and compiled it on two different linux boxes
with earlier versions of g++/egcs.
On one machine, which is running RedHat 5.2, I got:
/home/ezust/C++> ls -l a.out
-rwxrwxr-x 1 ezust ezust 75483 Nov 23 15:19 a.out
The compiler version is:
Reading specs from
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.90.29/specs
gcc version egcs-2.90.29 980515 (egcs-1.0.3 release)
On my desktop PC, which is running Mandrake 6.1, I got:
[ezust@ehost71 ~/C331]$ ls -l a.out
-rwxrwxr-x 1 ezust ezust 98983 Nov 23 17:19 a.out*
The compiler version is:
Reading specs from
/usr/lib/gcc-lib/i686-pc-linux-gnu/pgcc-2.91.66/specs
gcc version pgcc-2.91.66 19990314 (egcs-1.1.2 release)
It seems that the a.out files produced by the more recent Solaris compiler
contain library run code instead of dynamic links to library run code.
I must assume that something is wrong with our installation.
Can anyone give me some advice for fixing this?
Thanks!
---------------------------------------------------------------------
Paul Ezust Phone: (617) 573-8601
Department of Math & CS Fax: (617) 573-8591
Suffolk University *** Beacon Hill *** Boston, MA 02114-4280