Gcc 4.2.1 to be removed before FreeBSD 13, a firm timeline

Adrian Chadd adrian.chadd at gmail.com
Thu Dec 26 17:50:37 UTC 2019


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 at freebsd.org> wrote:
>
> On Tue, 13 Aug 2019 at 12:00, Warner Losh <imp at 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"


More information about the freebsd-arch mailing list