Date: Tue, 29 Mar 2022 13:05:15 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Piotr Kubaj <pkubaj@anongoth.pl> Cc: toolchain@freebsd.org Subject: Re: [Bug 261977] lang/gcc12-devel: enable LTO Message-ID: <4fda60eb-4cb1-d16b-c2c9-7ed52b9d07e7@pfeifer.com> In-Reply-To: <Yi1ZuqdsVnsrc3gt@KGPE-D16> References: <bug-261977-4076@https.bugs.freebsd.org/bugzilla/> <bug-261977-4076-RhPj6F1bct@https.bugs.freebsd.org/bugzilla/> <3590f79c-3a93-f8c-5e5-8aa484b358b5@pfeifer.com> <Yi1ZuqdsVnsrc3gt@KGPE-D16>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Mar 2022, Piotr Kubaj wrote: >> There is much, *much*, *MUCH* more important tasks around the lang/gcc* >> ports, and if anything this increases the risk for some of them. > I know, I'm currently also testing a patch for > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662 (for powerpc*) and > hope to send it to upstream some time soon. That's cool! I also saw you and Segher interacting around the recent GCC on FreeBSD/powerpc breakage, which also is great (not the breakage, of course, the engagement). >> If you can and want to help, updating GCC_DEFAULT from 10 and 11 is >> overdue, yet stuck: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378 > I may do it, but I prefer to add LTO to lang/gcc11 first (if there's no > pushback) to avoid potential breakage in case it doesn't work. But I > want to first check all those powerpc* hacks and workarounds that > accumulated in all the ports for the past couple of years. Probably > many of them are not needed anymore. That would be awesome indeed! > So... while I may help with GCC upgrade, currently other things are on > my mind. Keeping my fingers crossed this may bubble up your stack. :-) (Or that someone else volunteers, of course.) Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4fda60eb-4cb1-d16b-c2c9-7ed52b9d07e7>