Date: Sun, 12 Nov 2000 09:00:25 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-Id: <2950-Sun12Nov2000090025+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 In-reply-to: (message from Damian Yerrick on Sun, 12 Nov 2000 01:41:54 GMT) Subject: Re: DJGPP and Borland's compiler generated code size References: 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 Precedence: bulk > From: Damian Yerrick > Newsgroups: comp.os.msdos.djgpp > Date: Sun, 12 Nov 2000 01:41:54 GMT > > A DJGPP 200K binary includes: > o code to go into and out of protected mode > o code to "glob" filenames passed on the command line > o parts of DJGPP libc, which is large because it has to call DOS > services through DPMI, it's nearly POSIX compliant, and it's > optimized for speed (DOS calls through DPMI are _really_ expensive) > o your code, using 32-bit constants > o debugging information, which can be removed with strip.exe from > djdev203.zip A minor correction: strip.exe is part of GNU Binutils, not djdev. > A Borland 40K binary includes: > o a much smaller libc, optimized for size If that's a Windows compiler, most of the libc is not there, its in DLLs. > o your code, using 16-bit constants > o debugging information (unless you've turned it off) IIRC, debugging info is optional in Borland, it requires a command-line switch. If you don't use it, there's no debug info.