X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Fri, 6 Nov 2009 06:18:15 +0000 Message-ID: <416096c60911052218x1cca9a65w7e5b607175422f82@mail.gmail.com> Subject: small exe size increase from 1.7.0-62 to -63 From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com A test with an empty main compiled using gcc-4 under cygwin-1.7.0-63 has a size of 6.5K. After downgrading to 1.7.0-62, without changing anything else, the size goes down to 5.0K. $ cat test.c int main(void) { return 0; } $ gcc test.c -Os -s Looking at objdump differences, both code and data size have gone up: < SizeOfCode 00000800 < SizeOfInitializedData 00001000 --- > SizeOfCode 00000e00 > SizeOfInitializedData 00001600 And we're pulling in a bunch of additional functions from cygwin1.dll and kernel32.dll: > 515c 666 abort > 5170 788 cygwin_create_path > 51b0 812 dll_dllcrt0 > 51d4 1221 memcpy > 51ec 1620 strlen > 51f8 1742 vsnprintf > 5238 336 GetModuleFileNameW > 5274 388 GetStdHandle > 5284 798 VirtualProtect > 5296 801 VirtualQuery > 52a6 827 WriteFile Obviously 1.5K isn't much of a concern, but is this expected? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple