From: <SANDMANN AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Large .exe size
Date: Sat,  8 Mar 1997 23:36:48
Organization: Rice University, Houston, Texas
Lines: 10
Message-ID: <3321f810.SANDMANN@clio.rice.edu>
References: <5fcqps$pts$1 AT fep4 DOT clear DOT net DOT nz>
Reply-To: SANDMANN AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> Is there any non-standard way of reducing the startup code overhead?
> (ie after declaring null globbing funcs etc.) I am interested in
> making a certain exe as small as humanely possible, and was wondering
> what parts of the library source to attack for example.

Sure.  The TSR example does some of this triming for demonstration 
purposes and built to like 9K in size.  By replacing crt0.s and crt1.c
you can do anything.  An all assembly DJGPP image can be 2.5K in size
(rather silly thing to do).  Look at the libc source, remove what you
don't need, and you might be surprised how tiny your images can get!