delorie.com/archives/browse.cgi | search |
From: | ib AT wupperonline DOT de (Ingo Brueckl) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | version 2.03 binaries size problem |
Date: | Fri, 25 Aug 2000 20:02:00 +0200 |
Organization: | KDT and customers |
Lines: | 14 |
Message-ID: | <39a7068b@wupperonline.de> |
NNTP-Posting-Host: | line01e7.kdt.de |
X-Trace: | news.kdt.de 967234595 4740 195.8.238.231 (25 Aug 2000 20:16:35 GMT) |
X-Complaints-To: | abuse AT kdt DOT de |
NNTP-Posting-Date: | 25 Aug 2000 20:16:35 GMT |
X-Newsreader: | SlipDoor |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I was using djgpp 2.01 (with gpp2721b and bnu27b) for a project written in C++, which resulted in a binary of approx. (stripped) 177 KByte. Today I tried version 2.03 (with gpp2952b and bnu2951b) and got a binary size of (stripped) 271 KByte, which is a growth of more than 50% for the same sources! Does anyone know why the size increases that much?! What do I get for the extra 100 KByte? Maybe I should try a version 1.x to get an even smaller binary doing the same job? Ingo
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |