Date: Fri, 4 Apr 2014 18:44:08 +0500 From: Jordan Hubbard <jkh@ixsystems.com> To: David Chisnall <theraven@FreeBSD.org> Cc: svn-src-head@freebsd.org, Baptiste Daroussin <bapt@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org Subject: Re: svn commit: r264042 - in head: include lib/libc/gen lib/libc/include lib/libc/stdlib Message-ID: <B06E1588-8828-485F-A407-3F19231F8EA5@ixsystems.com> In-Reply-To: <152D73EE-DF9E-4757-B547-F1F22B12C824@FreeBSD.org> References: <201404021607.s32G7mhw051355@svn.freebsd.org> <20140404115256.GA85137@ivaldir.etoilebsd.net> <F2A33EA8-14F2-4D62-9021-9023A1751E48@FreeBSD.org> <8D6AF193-A5A3-4A28-A230-97A543395ACA@ixsystems.com> <2E0EC8CB-B3EE-4DB8-A33D-58FD2107F14D@FreeBSD.org> <6A02504F-5543-4F91-92F6-7B4FB9A34DC4@ixsystems.com> <152D73EE-DF9E-4757-B547-F1F22B12C824@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 4, 2014, at 5:55 PM, David Chisnall <theraven@FreeBSD.org> wrote: > We'd like to kill off gcc 4.2.1 in base, because it doesn't support = C11 or C++11. The lack of C++11 support is a problem because it means = gcc architectures can't build libc++, so they need to use an old = libstdc++ to build C++ things in the base system (which also means that = these things can't take advantage of C++11, which cleans up the language = a huge amount). The prerequisite for this is the availability of = external toolchains for the non-clang platforms. If we could build base = with gcc47 from ports, that would be okay, because then we'd have a = modern C/C++ compiler in the base system and a modern(ish - 4.8 / 4.9 = would be better, but 4.7 is a reasonable baseline) C/C++ compiler in = ports to drive an external toolchain. Ah, OK. And I=92m guessing there=92s been no interest in = forward-porting the blocks support to 4.7? That=92s kind of=85 a = bummer. I=92m guessing the great white hope for all the platforms is a = slow convergence on clang then? What is the compiler toolchain master = plan? If there=92s a wiki somewhere describing it, I=92d also be happy = to just go read that. > For embedded uses, we'd also like to build FreeBSD with = vendor's-ugly-hacked-up-gcc-of-the-week. This is less of an issue now = for ARM, but MIPS vendors still hack up gcc in such a way that there's = no way that they can get their changes upstreamed and then ship the = result with their chips. I see. That=92s pretty ugly indeed - is there a list of FreeBSD MIPS = folks doing this somewhere? I ask out of curiosity to know if there=92s = any collective attempt to chain them all together and insist that they = improve clang/MIPS to the point where they can stop doing ugly-ass gcc = ports. :) Thanks for all the info. It=92s very helpful! - Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B06E1588-8828-485F-A407-3F19231F8EA5>