delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/05/20/12:54:18

From: mdruiter AT cs DOT vu DOT nl (Ruiter de M)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gcc 2.8.1 outputs are much larger than gcc 2.7.2 ... why ??
Date: 20 May 1998 12:18:31 GMT
Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
Lines: 22
Message-ID: <6juhmn$arp$1@star.cs.vu.nl>
References: <6jr414$qgs$1 AT news DOT itri DOT org DOT tw>
NNTP-Posting-Host: galjas.cs.vu.nl
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Tony Kao (MacGyver AT ms11 DOT accmail DOT com DOT tw) wrote:
> with the compile option: gcc -o hello.exe hello.cpp -lstdcx
> I found the execution file size is 386560 bytes, which is much bigger than
> gcc 2.7.2 outputs. For gcc 2.7.2 the execution file size for the same
> program is 187675 bytes.

Are you sure? 2.8.x should generate bigger files (more debugging
info), but that much!?

> Anyone knows what's the extra information in the execution file ?? Or I
> missed any option ??

Most of the extra info is debugging info. It is necessary to know
"what code is where" in the executable, during debugging. Normally,
you don't need it. You can strip it off with `strip hello.exe', or
prevent it from being added with the `-s' linker option to gcc.

-- 
Groeten, Michel.        http://www.cs.vu.nl/~mdruiter
  ____________
  \  /====\  /          "You know, Beavis, you need things that suck,
   \/      \/           to have things that are cool", Butt-Head.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019