Date:	Fri, 02 Mar 2001 17:03:07 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	VJSuorsa AT Surfeu DOT Fi
Message-Id:	<2110-Fri02Mar2001170306+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC:	djgpp AT delorie DOT com, rprash AT wilco-int DOT com
In-reply-to:	<3a9f9e3c.1267.0@surfeu.fi> (VJSuorsa@Surfeu.Fi)
Subject:	Re: Fortran / C compiler precision and code pack
References:	<3a9f9e3c DOT 1267 DOT 0 AT surfeu DOT fi>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Mr. Veli Suorsa" <VJSuorsa AT Surfeu DOT Fi>
> Date: Fri, 2 Mar 2001 15:21:00 +0200
> 
> >What's wrong with 100KB?  Fortran has a large and complex
> >formatted I/O facility, and you pay for that with the
> >executable size. The bloat is additive, so large real-life
> >programs still get several tens of KBytes added.
> 
> I understand this largeness because of complex formatted I/O facility. But...
> 
> 
> >What is the problem with that, exactly?  How large did you
> >expect the program to be on disk?
> 
> When you use for example Microsoft fortran or pascal compilers, the
> test program exe size is 10-30 KB.

That's because this doesn't include the libraries: these compilers use
DLLs, whereas DJGPP programs are all statically linked.

> I will appreciate Djgpp compiler team, If you know how to optimize
> code to expected size.

It is already optimized if you use -O2 switch when compiling.

- Raw text -