Date: Tue, 19 Jul 2022 15:46:41 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 265254] lang/gcc11: build gets stuck Message-ID: <bug-265254-29464-ikUV1Age12@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265254-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-265254-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=3D265254 --- Comment #24 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Lorenzo Salvadore from comment #23) No one has to wait for any changes --if they are willing to use the OPTIONS to choose to avoid LTO_BOOTSTRAP or do other things like the FreeBSD build servers do. I'll note that my own reports here indicated a 1 min. load average of 18 for a 4 FreeBSD-cpu environment, somewhat more than 4*4. Not as extreme but still notable. But I knew about the behavior up front and my configurations are set up to deal with such high load average contexts. Note that GCC may be configurable: The confirmations in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106328 comments 2..4 by Richard Biener report: QUOTE GCCs WPA stage fork()s to write out LTRANS IL object files in parallel - th= ose processes are not controlled by make END QUOTE But it also reports a "--param lto-max-streaming-parallelism" that could be controlled now, without waiting for gcc changes, although I've never experimented with such. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265254-29464-ikUV1Age12>