Date: Sat, 16 Jul 2022 22:41:17 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 265254] lang/gcc11: build gets stuck Message-ID: <bug-265254-29464-wzhvgs9BJn@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 #7 from Yuri Victorovich <yuri@freebsd.org> --- (In reply to Lorenzo Salvadore from comment #5) > While I also would like to disable LTO by default, others consider that L= TO should be enabled by default so that official packages are built as opti= mized as possible, while users building their own ports should just disable= the option if they are unhappy with it. The problem is not that LTO is "very resource consuming". The problem is th= at GCC mal-parallelized the build and it is spawning exceedingly many processe= s. Such mal-parallelization is a pitfall of GNU Make. All one has to do is to = use -jN at multiple levels of the directory hierarchy and similar effect would = be achieved. They should fix the bug first before others use this feature. I am not sure why this buggy feature was enabled in the FreeBSD port in the first place. --=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-wzhvgs9BJn>