Date: Thu, 17 Nov 2016 03:27:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214456] lang/gcc6: -r424540: FreeBSD's full bootstrap fails the stage 2 vs. 3 comparison the build stops (powerpc 32-bit anyway) Message-ID: <bug-214456-13-Lgpg984CwM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214456-13@https.bugs.freebsd.org/bugzilla/> References: <bug-214456-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214456 --- Comment #8 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #7) I looked at a armv6 example (which did not fail the comparison). It also has (read-rtl.c example): Stage 2: -g -gtoggle Stage 3: -g Being successful for the comparison it does not leave . . ./work/. . . havi= ng copies of the likes of the compared stage2 and stage3 read-rtl.o files : ju= st the one final one at . . ./work/.build/gcc/build/read-rtl.o . Still it suggests that Stage 2 had debug information turned off by -gtoggle while Stage 3 had it turned on --yet the comparison passed. Unfortunately this might mean having to look at the details of the comparis= on technique for powerpc and the data it was processing to find what makes it classify its read-rtl.o's as mismatched. Merely noting the variations in having debug information vs. not is apparen= tly not enough to have a mismatch as the classification. Bad assumption on my p= art, just like the tie to WITH_DEBUG was a bad assumption on my part. Still 32-bit powerpc does fail its comparison so the bugzilla report still applies overall. It just would read better and quicker if I could eliminate= my false assumptions from the description and comments. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214456-13-Lgpg984CwM>