Date: Thu, 5 Oct 2017 16:28:44 -0700 From: Warner Losh <imp@bsdimp.com> To: "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Making C++11 a hard requirement for FreeBSD Message-ID: <CANCZdfq5=KRp4NYKsc15gyS9C7CxrBFxcKQLPwnb_0oPb15vJw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I'd like to start a conversation about the viability of making C++11 a hard requirement for bootstrapping FreeBSD and setting a specific deadline for doing so. This discussion is motivated by an ask from the jemalloc folks to use a limited subset of C++11 inside of malloc in such a way that is C safe (so the C programs wouldn't bloat with a C++ runtime). That's an ongoing discussion in another forum, and isn't appropriate for this thread because this has become a frequent request (but if you have opinions, please find the thread in current@ about it). I don't know the timeline of their plans to do this. I'd like to take the rather vague plans we've had "before 12" and create a timeline for removal of gcc 4.2 coupled with a requirement for support in clang or a working external toolchain. This requirement would be coupled with the requirement that the external toolchain support C++11 constructs. I'd like to propose we do this 12/31/17. Any architectures that can't meet this timeline will be disconnected from universe at that time and deleted 3/31/18. It's my belief that i386, amd64, arm, aarch64, powerpc and powerpc64 are ready for this change and mips* would be ready for this change with an external clang toolchain. I'm unsure of riscv and sparc64, but suspect that a newer version of gcc as an external toolchain could work. Comments? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfq5=KRp4NYKsc15gyS9C7CxrBFxcKQLPwnb_0oPb15vJw>