Date: Mon, 28 Mar 2022 10:29:42 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <bug-261977-29464-4lFDtKyUfy@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 #12 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Matthias Andree from comment #11) Careful with size calculations: my figures were for a 16 core system using all the cores. I've not investigated if, say, a 4 core system using all its cores would use more like 1/4 the memory or not. It would not get as many ld's going at once and I do not know the relative sizes of the various ld's that might overlap in time for whatever the configuration is. The same sort of point goes for the memory use for bootstrap-debug style builds: it was the same 16 core type of context. General expectations of relatively bigger vs. smaller memory use between the two bootstrap-* styles is likely very reasonable. But I do not know about detailed sizing relationships across a variety of contexts. I only got into testing this as a way to provide some background information for: https://lists.freebsd.org/archives/freebsd-toolchain/2022-March/000450.html where Dimitry Andric did not have direct access to information he wanted about a recent build failure on a FreeBSD aarch64 server. I do not really plan on doing more in this bugzilla submittal's comments. I've provided my evidence about tradeoffs and presented my points. I'm unclear which mechanism would be appropriate to express picking the bootstrap-* style to use. --=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-4lFDtKyUfy>