[Scummvm-devel] Daily/nightly Win32 builds

[D G Turner]

On 06/16/11 13:57, Michael Madsen wrote:
>> -----Original Message-----
>> From: Max Horn [mailto:max at quendi.de]
>> Sent: Thursday, June 16, 2011 2:42 PM
>> To: Michael Madsen
>> Cc: ScummVM Development list
>> Subject: Re: [Scummvm-devel] Daily/nightly Win32 builds
>>
>> Hi again,
>>
>> just to play some more with this, I did a manual mingw32 build on buildbot,
>> with all engines (except sword25) enabled, and got a 182 MB binary. Then I
>> let the "size" command run on it:
>>
>> ~/scummvm/builds/mingw32-allengines$ i586-mingw32msvc-size -A scummvm.exe
>> scummvm.exe  :
>> section                size        addr
>> .text              14882256     4198400
>> .data                135412    19083264
>> .rdata              2529472    19222528
>> .bss                1170704    21753856
>> .idata                 6836    22925312
>> .rsrc               3763680    22933504
>> .debug_aranges       405096    26697728
>> .debug_pubnames     3613774    27103232
>> .debug_info       143163527    30720000
>> .debug_abbrev       2840076   173887488
>> .debug_line         2907566   176730112
>> .debug_frame        2700452   179638272
>> .debug_str          2470720   182341632
>> .debug_loc          3530976   184815616
>> .debug_ranges           528   188350464
>> Total             184121075
> 
> For reference: 
> C:\scummvm\scummvm>size -A scummvm.exe
> scummvm.exe  :
> section               size       addr
> .text             14827876    4198400
> .data               119364   19030016
> .rdata             2585184   19152896
> .bss               1187328   21741568
> .idata                7624   22929408
> .CRT                    24   22937600
> .tls                    32   22941696
> .rsrc              3771664   22945792
> .debug_aranges      406496   26718208
> .debug_pubnames    3636249   27127808
> .debug_pubtypes       4433   30765056
> .debug_info       47734428   30773248
> .debug_abbrev      1888615   78508032
> .debug_line        2608446   80400384
> .debug_frame       2725452   83009536
> .debug_str         1000470   85737472
> .debug_loc         3622355   86740992
> .debug_ranges       660232   90365952
> Total             86786272
> 
> C:\scummvm\scummvm>gcc -v
> Using built-in specs.
> Target: mingw32
> Configured with: ../gcc-4.3.3/configure --prefix=/mingw --build=mingw32 --enable-languages=c,ada,c++,fortran,objc,obj-c++ --with-bugurl=http://www.tdragon.net/recentgcc/bugs.php --disable-nls --disable-win32-registry --enable-libgomp --disable-werror --enable-threads --disable-symvers --enable-cxx-flags='-fno-function-sections -fno-data-sections' --enable-fully-dynamic-string --enable-version-specific-runtime-libs --enable-sjlj-exceptions --with-pkgversion='4.3.3-tdm-1 mingw32'
> Thread model: win32
> gcc version 4.3.3 (4.3.3-tdm-1 mingw32)
> 
> I'm afraid I don't have any bright ideas other than attempting to upgrade the cross-compiler, but I have no idea how to go about that.

These might be of help to try to analyse the .debug_info, which I think
contains the DWARF output:

http://wiki.dwarfstd.org/index.php?title=Libdwarf_And_Dwarfdump
http://www.mingw.org/wiki/Large_executables

As the second link indicates, it may be that some of the external or
toolchain libraries were compiled with -g and these symbols are being
included into the .debug_info segment, but I'm not a compiler expert.

-- 
Thanks,
David Turner