Date: Thu, 30 Apr 2020 20:43:14 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 245511] lang/gcc9: build with base GCC on powerpc64 elfv1 Message-ID: <bug-245511-25139-jWOfsik1du@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245511-25139@https.bugs.freebsd.org/bugzilla/> References: <bug-245511-25139@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=3D245511 --- Comment #12 from Gerald Pfeifer <gerald@FreeBSD.org> --- (In reply to Piotr Kubaj from comment #9) Thank you for those tests, Piotr. The results look concerning indeed, I wonder what the quality of the produced compiler is. :-( Just to make sure, what were the last lines coming from gmake, that is those looking like gmake[3]: *** [mode-switching.o] Error 1 gmake[3]: Leaving directory `/files/pfeifer/OBJ-0131-2308/gcc' gmake[2]: *** [all-stage2-gcc] Error 2 gmake[2]: Leaving directory `/files/pfeifer/OBJ-0131-2308' gmake[1]: *** [stage2-bubble] Error 2 gmake[1]: Leaving directory `/files/pfeifer/OBJ-0131-2308' where I am mostly interested in those with the "***"? I am wondering whether this misses where the actual issue happens, since the docs say the following: If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when doing @samp{make}. And they also say: Again, if the native compiler miscompiles the stage1 compiler, you may need to work around this by avoiding non-working parts of the stage1 compiler. Use @code{STAGE1_TFLAGS} to this end. So I am wondering whether you should not have tried setting STAGE1_TFLAGS in the first place, to avoid a broken stage1 compiler as opposed to trying to be gentle to a broken stage1 compiler by only invoking it with -O0. Do you see what I mean? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245511-25139-jWOfsik1du>