This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 13 Mar 2009 16:05:23 +0000
- Subject: Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2
- References: <49B90A2B.3050907@alice.it> <49BA7A8E.3070207@alice.it>
Angelo Graziosi wrote:
> Dave Korn wrote:
>
>> Can you show me the "objdump -h" output for both?
>
> It seems that here there is a problem. I have build with the same build
> script and without debug info, but, for what I can understand, with gcc4
> the debug info are still there. To reproduce:
From what I understand, with gcc3 the debug info are also still there:
> ============================ GGG 3.4.4-999 ========================
>
> ./configure --enable-everything --disable-debug
> 5 .stab 0004e2c4 00447000 00447000 00044000 2**2
> CONTENTS, READONLY, DEBUGGING, EXCLUDE
> 6 .stabstr 0002db31 00496000 00496000 00092400 2**0
> CONTENTS, READONLY, DEBUGGING, EXCLUDE
... just a whole lot smaller than with gcc4:
> ============================ GGG 4.3.2-2 ========================
>
> CC='gcc-4' CXX='g++-4' CPP='cpp-4' ./configure --enable-everything
> --disable-debug
> 5 .debug_aranges 000003c0 00448000 00448000 00043c00 2**3
> CONTENTS, READONLY, DEBUGGING
> 6 .debug_pubnames 00002c7f 00449000 00449000 00044000 2**0
> CONTENTS, READONLY, DEBUGGING
> 7 .debug_info 00106f9e 0044c000 0044c000 00046e00 2**0
> CONTENTS, READONLY, DEBUGGING
> 8 .debug_abbrev 00005bbe 00553000 00553000 0014de00 2**0
> CONTENTS, READONLY, DEBUGGING
> 9 .debug_line 0000ae50 00559000 00559000 00153a00 2**0
> CONTENTS, READONLY, DEBUGGING
> 10 .debug_frame 0000378c 00564000 00564000 0015ea00 2**2
> CONTENTS, READONLY, DEBUGGING
> 11 .debug_str 00005371 00568000 00568000 00162200 2**0
> CONTENTS, READONLY, DEBUGGING
> 12 .debug_loc 00020b56 0056e000 0056e000 00167600 2**0
> CONTENTS, READONLY, DEBUGGING
> 13 .debug_ranges 000023a0 0058f000 0058f000 00188200 2**0
> CONTENTS, READONLY, DEBUGGING
So I think you should check for a bug in the --disable-debug configure
option. Running strip on the exe as a separate step should work around the
problem too. Taking a look at the actual content:
> ============================ GGG 3.4.4-999 ========================
> 0 .text 00035230 00401000 00401000 00000400 2**4
> CONTENTS, ALLOC, LOAD, READONLY, CODE
> 1 .data 00001f40 00437000 00437000 00035800 2**5
> CONTENTS, ALLOC, LOAD, DATA
> 2 .rdata 00009f80 00439000 00439000 00037800 2**5
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 3 .bss 00000410 00443000 00443000 00000000 2**3
> ALLOC
> 4 .idata 000027cc 00444000 00444000 00041800 2**2
> CONTENTS, ALLOC, LOAD, DATA
> ============================ GGG 4.3.2-2 ========================
> 0 .text 00036138 00401000 00401000 00000400 2**4
> CONTENTS, ALLOC, LOAD, READONLY, CODE, DATA
> 1 .data 000017c0 00438000 00438000 00036600 2**5
> CONTENTS, ALLOC, LOAD, DATA
> 2 .rdata 00009484 0043a000 0043a000 00037e00 2**5
> CONTENTS, ALLOC, LOAD, READONLY, DATA
> 3 .bss 00000430 00444000 00444000 00000000 2**3
> ALLOC
> 4 .idata 000027ec 00445000 00445000 00041400 2**2
> CONTENTS, ALLOC, LOAD, DATA
... it seems that the actual overall size of the stripped exes should be
pretty much the same betwen the two compilers.
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/