Date: Tue, 19 Apr 2022 16:47:51 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <bug-261977-29464-RtBkS6Ye8w@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 #19 from Robert Clausecker <fuz@fuz.su> --- (In reply to Piotr Kubaj from comment #18) Built times are not super relevant as long as they stay in a reasonable ran= ge.=20 Waiting 3 days for the compiler to build is not reasonable. And as I said, this is both for native and for cross builds from reasonably fast hardware. Whenever there is some sort of update to the ports tree that changes a dependency of gcc, Poudriere recompiles gcc. So excessive build times significantly interfere with my ability to test ports. Right now I do not change any build flags nor do I provide any custom optio= ns because if I did, my test results would not be applicable. And even for normal, source-building users (which do exist), waiting three = days for a compiler to be built is completely unreasonable. And that's the time= up until now. The compiler build has not finished yet and I don't know when it will. Have you weighed the extra build time against the performance advantage this brings? How much does the LTO-built gcc speed up build times in comparison= to a normally built (or even non-bootstrapped) gcc? --=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-RtBkS6Ye8w>