[Bug 261977] lang/gcc12-devel: enable LTO

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261977

--- Comment #31 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Mark Millard from comment #28)

As for what I can get for aarch64 . . .

http://ampere2.nyi.freebsd.org/build.html?mastername=main-arm64-default&build=p1853d90f79b6_s27ac4281fd

actually has both gcc1[12]-devels in LTO style built successfully in
a 30,000+ port bulk -a . (Seems rare for the 30,000+ bulks on aarch64.)

where: 115:50:28

vs. [predating the LTO style use (Feb.)].

http://ampere2.nyi.freebsd.org/build.html?mastername=main-arm64-default&build=pde1a3d3a0c66_sa4a31271cc

where: 107:17:11

So, like amd64, not a huge difference in the time scale --for how
the FreeBSD servers are used-- but an increase observed.

But the increases for amd64 and aarch64 are small enough to not be
clearly mostly-gcc-LTO related for the cause of the variation.
Still, it would not be surprising for LTO being a contribution,
just not huge for the overall time involved.

As near as I can tell, unless having gcc11 as the default and
built via LTO so more ports wait and that changes things
significantly, having LTO used on the FreeBSD servers looks
reasonable relative to how other aspects are (and have been)
handled.

[A context configured to allow for high load averages relative to
hardware threads and large RAM+SWAP to match (avoiding processing
slack) might get significantly different results. But that is not
how FreeBSD build servers are used.]

-- 
You are receiving this mail because:
You are on the CC list for the bug.