Making C++11 a hard requirement for FreeBSD

[A. Wilcox]

On 05/10/17 18:41, Brooks Davis wrote:
> On Thu, Oct 05, 2017 at 04:28:44PM -0700, Warner Losh wrote:
>> 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.
> 
> If someone wants to test sparc64, that's fine, but with Oracle laying
> off the SPARC it's arguably more dead than IA64 was when we removed it
> (Intel shipped the last design *this* May).
> 
> -- Brooks
> 

Thinking out loud:

That doesn't change the fact that sparc64 still exists, and with Oracle
laying off Solaris as well, FreeBSD becomes a "way out" for people
heavily invested (DC full of sparc64 gear, or such).  That could make
the sparc64 port not only more widely used, but more widely tested, with
more potential developers.

Or maybe not.

I can't see the future :)

--arw

-- 
A. Wilcox (awilfox)
Open-source programmer (C, C++, Python)
https://code.foxkit.us/u/awilfox/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20171005/28fc2ed3/attachment.sig>