Date: Fri, 23 Aug 2013 07:59:11 -0600 From: Warner Losh <imp@bsdimp.com> To: David Chisnall <theraven@FreeBSD.org> Cc: toolchain@FreeBSD.org, Kurt Jaeger <lists@c0mplx.org>, current@FreeBSD.org Subject: Re: GCC withdraw (was: Re: patch to add AES intrinsics to gcc) Message-ID: <04A68472-3377-4E48-B7BE-DDBF070507B4@bsdimp.com> In-Reply-To: <BB752B11-C001-493E-BFC7-CD0C7CFAC0C5@FreeBSD.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <F2129B51-C112-49C3-ABB5-89562C23F21A@bsdimp.com> <BB752B11-C001-493E-BFC7-CD0C7CFAC0C5@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 23, 2013, at 7:54 AM, David Chisnall wrote: > On 23 Aug 2013, at 14:52, Warner Losh <imp@bsdimp.com> wrote: >> No. That breaks non x86 architecutres. gcc must remain in base for = now, or there's no bootstrap ability. Nobody has done the lifting to = cleanly integrate gcc as a port into buildworld, althogh Brooks' work = gets us most of the way there. >=20 > We've been using brooks' work to build the base system with an = out-of-tree toolchain for some time now... I'll have to try the native build part of the cycle then... Early = versions of the patch failed when you cross built the target, installed = the target, but wound up with no compilers to bootstrap the external = toolchains with to do native builds on the target. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04A68472-3377-4E48-B7BE-DDBF070507B4>