Date: Wed, 20 Apr 2022 01:55:54 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <bug-261977-29464-tiUS7p0M0Q@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261977-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-261977-29464@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=3D261977 --- Comment #40 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Piotr Kubaj from comment #35) Note: I agree that most FreeBSD build server activity for building lang/gcc*'s (gcc11+) can reasonably use LTO style. But there is a reason for the "most" . . . To my knowledge, no FreeBSD build server targeting armv6 or armv7 has ever had such a LTO build of a gcc* complete, one reason being because after the first stage bootstrap, it is nearly all via QEMU, possibly leading to 100+ hours being needed for a build (!no good data!). In other words, these two target architectures did not meet the Comment #4 criteria: QUOTE Let's see whether it builds now fine for all the packaged architectures and versions. END QUOTE Avoiding the LTO style builds targeting armv6 or armv7 may well be reasonable for the FreeBSD build servers and for other contexts targeting armv6 or armv7. To my knowledge, the rest of architectures that the FreeBSD servers target avoid needing to use QEMU (or analogous) and so avoid the related issues. --=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-261977-29464-tiUS7p0M0Q>