Date: Thu, 26 Dec 2019 17:50:37 -0000 From: Adrian Chadd <adrian.chadd@gmail.com> To: Ed Maste <emaste@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Gcc 4.2.1 to be removed before FreeBSD 13, a firm timeline Message-ID: <CAJ-VmonRVP4%2BNU3Du_e9vZaL-vnc3V9r87_2mV0==KgCTKhDEA@mail.gmail.com> In-Reply-To: <CAPyFy2Dwasf1NDu-AeiC=BkY2zU5UFL-0-k34ce7qh6EEovAMw@mail.gmail.com> References: <CANCZdfrZ-C37c7Eso7NrtMG5_kv3T9qO3c3k8xcgEeTCrY3nQg@mail.gmail.com> <CAPyFy2Dwasf1NDu-AeiC=BkY2zU5UFL-0-k34ce7qh6EEovAMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
mips64el ? Hm, interesting. I thought I had already tested all the mips/mips64 variants with an external gcc toolchain. Lemme go see. -adrian On Wed, 18 Dec 2019 at 13:03, Ed Maste <emaste@freebsd.org> wrote: > > On Tue, 13 Aug 2019 at 12:00, Warner Losh <imp@bsdimp.com> wrote: > > > > Greetings, > > > > As promised for almost the past decade or so, gcc 4.2.1 will be removed > > from the tree before FreeBSD 13 is branched. > > > ... > > 2019-12-31: Turn off gcc 4.2.1 build by default (can be turned on) > > Reminder, this is less than two weeks away. In my no-gcc-4.2.1 > experiments sparc64, mips64el and mips64elhf are currently failing. > Turning off GCC 4.2.1 won't immediately cause their eviction, but the > clock is running for them to be fixed or removed: > > > 2020-03-31: svn rm gcc 4.2.1 and friends > > > > 2020-05-31: svn rm all non-clang platforms not supported by in-tree LLVM or > > converted to ext toolchain. > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonRVP4%2BNU3Du_e9vZaL-vnc3V9r87_2mV0==KgCTKhDEA>