This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/81926] go/parse.o differs between stage2 and stage3
- 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, 29 Aug 2017 12:40:09 +0000
- Subject: [Bug bootstrap/81926] go/parse.o differs between stage2 and stage3
- Auto-submitted: auto-generated
- References: <bug-81926-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81926
--- Comment #18 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Sorry for the long delay: I've been mostly away for 6 weeks, only now
> catching up.
Really no need to apologize...
> I've been seeing similar bootstrap comparison failures on Solaris/SPARC,
> but only when using /bin/as. I tend to forget about them since most of
> my bootstraps are done with contrib/regression/btest-gcc.sh which mostly
> hides them ;-(
>
> I had analyzed this in the past already. Here's what I found, and just
> reconfirmed for the smallest differing file in a sparc-sun-solaris2.11
> bootstrap, gcc/ada/table.o in my case:
>
> * with -gtoggle (stage2), there's no .text section in the assembler
> output
>
> * without -gtoggle (stage3), the assembler output gets
OK, but it's a regular bootstrap, aka bootstrap-debug. Now, on Solaris, it's
very easy to get an old-style bootstrap because objdump or equivalent is not in
the path so you end up comparing the debug info in stage2 and stage3, which
means additional comparison failures. See PR bootstrap/77995 for example.
Dennis, can you confirm that BUILD_CONFIG is defined to an empty value in the
toplevel config.log file of the original boostrap?