Date: Tue, 19 Apr 2022 16:27:11 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <bug-261977-29464-3E4U2uZbb5@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 #18 from Piotr Kubaj <pkubaj@FreeBSD.org> --- (In reply to Robert Clausecker from comment #17) Are build times that relevant? Sure, if you insist on building manually on a slow hardware, it's going to be painful, but we have binary packages for su= ch users. IMO faster and smaller packages for everyone is worth it and we have package cluster exactly to allow users to easily install ready-to-use packages. If for some reason builds time out on the cluster (don't know, didn't check= ), then you should open a new PR to ask portmgr@ to increase timeouts (or maybe use more threads to build gcc). Since I'm not in portmgr@, I can't do that. Although I was not around at that time, I believe when -O2 was added to def= ault flags, many people also complained about that, due to more resources being used, but after all, it was worth the cost. Or do you also add -O0 to your builds to make them faster? --=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-3E4U2uZbb5>