This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/81926] go/parse.o differs between stage2 and stage3 for gcc 7.2.0
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 22 Aug 2017 21:16:09 +0000
- Subject: [Bug go/81926] go/parse.o differs between stage2 and stage3 for gcc 7.2.0
- Auto-submitted: auto-generated
- References: <bug-81926-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81926
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> elfdump in Solaris says stage2 section ".debug_info" size is 0x1636a2:
>
> Section Header[37]: sh_name: .debug_info
> sh_addr: 0 sh_flags: 0
> sh_size: 0x1636a2 sh_type: [ SHT_PROGBITS ]
> sh_offset: 0x1faa0 sh_entsize: 0
> sh_link: 0 sh_info: 0
> sh_addralign: 0x1
>
> Whereas stage3 reports :
>
> Section Header[37]: sh_name: .debug_info
> sh_addr: 0 sh_flags: 0
> sh_size: 0x163698 sh_type: [ SHT_PROGBITS ]
> sh_offset: 0x1faa0 sh_entsize: 0
> sh_link: 0 sh_info: 0
> sh_addralign: 0x1
>
>
> Not exactly 8 bytes. Looks like 10 bytes diff. All other "sh_size" section
> size data matches.
OK, thanks, this rings a bell. Unlike other platforms, the bootstrap process
on Solaris involves comparing the debug info, so things like this might go
unnoticed by the developers using other platforms.