2009/9/28 Tyson Roberts: >> Some observations regarding 64 bit MacVim: >> >> 1. File sizes in 64 bit: >> >> -rwxr-xr-x 1 winckler staff 613928 Sep 27 21:57 MacVim >> -rwxr-xr-x 1 winckler staff 2475280 Sep 27 21:57 Vim >> >> ... and 32 bit: >> >> -rwxr-xr-x 1 winckler staff 334344 Sep 2 14:31 MacVim >> -rwxr-xr-x 1 winckler staff 2083056 Sep 2 14:31 Vim >> >> Seems the MacVim binary almost _doubles_ in size! (Why?) > > Is it possible that you're doing a dual compile 64/32 bit and the code > size is doubling because you have a darwin binary containing both? A > quick command line should check that, but if it is in fact doubling in > size, I have no answers other than some peculiarity about how MacVim > declares things (are you somehow compiling the entire code into an int > array and then operating off of it? :D).
Actually, it would have to be a long array as I just found out [1] -- ints are still 4 bytes LP64. :-) I scratched my head after posting that, so I decided to do another clean build of 32 bit MacVim and I got this: -rwxr-xr-x 1 winckler staff 495288 Sep 27 22:35 MacVim -rwxr-xr-x 1 winckler staff 2196224 Sep 27 22:35 Vim Both builds (64bit/32bit) were one architecture only, debug mode, Vim with normal features only. However, I still don't understand why file sizes are so different: the first 32 bit binary was also a debug build [or at least so I thought...maybe it is not] and it is much smaller (apparently its not a 64 bit vs 32 bit problem though). Björn [1] Table 2-1: http://developer.apple.com/mac/library/documentation/Darwin/Conceptual/64bitPorting/transition/transition.html --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
