Date: Thu, 29 Aug 2013 10:02:54 -0600 From: Warner Losh <imp@bsdimp.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: current@freebsd.org, Volodymyr Kostyrko <c.kworr@gmail.com>, toolchain@freebsd.org, John-Mark Gurney <jmg@funkthat.com> Subject: Re: patch to add AES intrinsics to gcc Message-ID: <D4CCE860-A8C2-4CBB-8DFF-68B2DF6283F0@bsdimp.com> In-Reply-To: <521CBBDE.6030503@freebsd.org> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <CAE-m3X324rbdP_C=az4eO-EkMcR-yFAeRG7S4q%2BMUsnMezGddw@mail.gmail.com> <521751AF.6040905@gmail.com> <alpine.LNX.2.00.1308260329190.3920@trevally.site> <521CBBDE.6030503@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 27, 2013, at 8:46 AM, Nathan Whitehorn wrote: > On 08/25/13 18:41, Gerald Pfeifer wrote: >> On Fri, 23 Aug 2013, Volodymyr Kostyrko wrote: >>> I object. Many ports that compiles perfectly on gcc 4.2.1 can't be=20= >>> compiled with lang/gcc. I checked this once and the number of ports=20= >>> that require strictly gcc 4.2.1 was bigger for me then number of=20 >>> ports that can't be compiled with clang but fill fine on lang/gcc. >>>=20 >>> I'll gonna recheck whether lang/gcc42 is sufficient for them. But I=20= >>> have that bad feeling... >> If there are ports that use USE_GCC=3Dany and do not build with >> lang/gcc, these should have USE_GCC=3D4.2 -- without a '+'! -- >> not USE_GCC=3Dany. >>=20 >> It'll be great if you can fix any such port. >=20 > It would be particularly nice if we had a port with FreeBSD's many > patches to 4.2. lang/gcc42 (and 46 and lang/gcc) do not build on > powerpc64, for example, while our in-tree GCC does. I think it would be more than "nice" to have. I'd argue that these = issues need to be addressed before we can claim to have a full = external-supported toolchain story that's integrated and well tested and = covers the needs of all our users. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4CCE860-A8C2-4CBB-8DFF-68B2DF6283F0>