Date: Tue, 19 Apr 2022 16:51:56 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <bug-261977-29464-6F1lb3ngOm@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 #20 from Matthias Andree <mandree@FreeBSD.org> --- (In reply to Piotr Kubaj from comment #18) Build times are super relevant if we want to keep any faint trace of manpow= er working on ports. For regular work on any of my ports, the usual *re*build set comprises 300 = to 900 ports, and I have jumped through hoops for MONTHS to deal with the excessive RAM and disk space use of, usual offenders, webkit, rust (because it's a requisite to one of the popular graphics libraries), and usually at least two versions EACH of llvm and gcc, although I do not build ${COMPILER}-devel ports. That also means that I spend one day setting the tables for ports work and = then a very short time doing my ports work, test, commit, and then hope that a g= it pull --rebase won't break my port when one of its upstream requisites chang= ed again. --=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-6F1lb3ngOm>