Date: Mon, 26 Aug 2013 15:14:55 +0200 From: Claude Buisson <clbuisson@orange.fr> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: re@freebsd.org, current@freebsd.org Subject: Re: patch to add AES intrinsics to gcc Message-ID: <521B54CF.3020905@orange.fr> In-Reply-To: <alpine.LNX.2.00.1308260306080.3920@trevally.site> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <CAE-m3X324rbdP_C=az4eO-EkMcR-yFAeRG7S4q%2BMUsnMezGddw@mail.gmail.com> <5CE4B5FA-9DA0-45E4-8D67-161E0829FE6B@FreeBSD.org> <5217DBAB.5030607@freebsd.org> <86032E72-A569-4946-B4F8-26F687067B31@bsdimp.com> <1380949A-254A-4222-BEDE-0C23E16E4F67@freebsd.org> <8C31A000-6806-4291-98A4-E8291E637BD2@bsdimp.com> <CAJ-Vmo=p%2B81StQoHAKV-xHueNc7oRzsmm4a-5FuvK2qHX%2BWKXA@mail.gmail.com> <CAOFF%2BZ1bAr4M5BM2=QKGz0D-3OHhHoTCUv8qRmxnsvz2gd64-Q@mail.gmail.com> <CE2DCF04-3E81-4FFB-AEB4-CD788420D84E@bsdimp.com> <alpine.LNX.2.00.1308260306080.3920@trevally.site>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/26/2013 03:12, Gerald Pfeifer wrote: > On Sat, 24 Aug 2013, Warner Losh wrote: >>> "If you push gcc out to a port, and you have the 'external compiler' >>> toolchain support working correctly enough to build with this, why >>> don't we just push clang out to a port, and be done with it?" >> This is a stupid idea. It kills the tightly integrated nature of >> FreeBSD. I'd say it is far too radical a departure and opens up a >> huge can of "which version of what compiler" nightmare that we've >> largely dodged to date because we had one (or maybe two) compilers >> in the base system. > > I am working towards establishing lang/gcc as _the_ version of GCC > to use for ports. > > Today I looked at a couple of those GCC cross-compilers we have in > ports, and I have to admit I am not thrilled. Each of those I saw > copies a lot from (older version of my ports), each has a different > maintainer, each has some additions, and there is little consistency. > Perhaps you could have a look at the fact that lang/gcc is at 4.6.3, and lang/gcc46 is no more a snapshot but a true release 4.6.4. IMHO, lang/gcc must be discontinued, or updated to 4.6.4 and lang/gcc46 discontinued ? > Are these the base of 'external compiler' toolchain support? Are > there any plans to increase consistency and reduce redundancy? In > an ideal world, could those become slave ports of lang/gcc? > > Gerald Claude Buisson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?521B54CF.3020905>