From owner-freebsd-arch@FreeBSD.ORG Sun Jan 13 13:24:11 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 01CCC6EC; Sun, 13 Jan 2013 13:24:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 97FCE61A; Sun, 13 Jan 2013 13:24:10 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r0DDO363039788; Sun, 13 Jan 2013 15:24:03 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r0DDO363039788 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r0DDO2VF039787; Sun, 13 Jan 2013 15:24:02 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 13 Jan 2013 15:24:02 +0200 From: Konstantin Belousov To: Peter Wemm Subject: Re: how long to keep support for gcc on x86? Message-ID: <20130113132402.GR2561@kib.kiev.ua> References: <20130112233147.GK1410@funkthat.com> <20130113014242.GA61609@troutmask.apl.washington.edu> <20130113053725.GL1410@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="en9/O5YN3eJ0yPaf" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Adrian Chadd , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 13:24:11 -0000 --en9/O5YN3eJ0yPaf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 13, 2013 at 12:09:09AM -0800, Peter Wemm wrote: > On Sat, Jan 12, 2013 at 11:44 PM, Adrian Chadd wrote: >=20 > > Thus I think adding clang-only code to the system right now is very, > > very premature. There still seem to be reasons to run systems on GCC > > instead of clang. >=20 > I don't have a problem with it so long as the system isn't *broken* if > you're not using clang. ie: if the status-quo is maintained for gcc > systems and g-faster bits are enabled with clang. It's fine to > provide incentives to try clang, but it is not ok to regress the gcc > case. Absolutely agree. Please note that in the AES-NI case, gcc 'support' is only partially gcc issue, if gcc at all. Our 2.17 gas does not know about AES-NI mnemonics and cannot assemble them. AFAIR the patch uses C built-in for AES-NI and SSE3 or 4, which I think could be implemented manually in the amount needed for the patch, for old gcc. >=20 > eg: we did the same with gcc in the early days, or at least made a > token effort. eg: you got __asm __inline with gcc, or regular > assembler functions if not. It was never complete though. >=20 > I use clang in general (and WITHOUT_GCC), but not on lower end > machines like Atom boxes. They don't have AES-NI anyway. --en9/O5YN3eJ0yPaf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJQ8rVwAAoJEJDCuSvBvK1BbcMQAJsAXyPX490PyqybhYkyKaui Wrh02YluVeWtQcZS9Y420/YdOzjjcEh3L69vqFaTSzI07HMvQAs95p0AmtrwLTq0 i1HhoRCcxIhXpw6M1IZtoy0QU+GW3jFaliUgWfUxUbjnS+L3jPp1ZXolovxIE2J2 R90hkLOML3mDSMyp3lGWArAAfmNAr45E94XawZ67PqWT/tXqqYrbNqhHytcEWbH+ 1Yv76JFpiLAxewblCZ64u53mynHOrbUPza4fbDMP4vwic8K/zZ8xgF91UNrgOiGH /DkF7iIhdIXeABIb66LLIkzpVDUUrgjUVOOtymgEU8HaSotM+1zt/16BeLUqLPdE u/EQdwn3sSANQbx6G44B4slTeV9a0TOpq2+hm0RueDjhpNKoPWiaGSKQJlA5mXAE PNYVy7vjtjZTXPO2QVxQS6Eehnim0RWfBe8INi04AzUDVolkethoXd8eu6ZnkiBG brsGbxDKOKnCZvVSMG/+3Wz16tGk3BmoprYmXawR9vMZUP6yYyVptcSUhdPBVhoq Qd7ye6sH2IcFzI+WuZopG5JNGdl+rMegEfk6ttvX4+XN3VJQfKsYwX7V/vIW1+0Q Im3hcnj9UtlimVi5OgGGVO+Qe1GHErl4vyEjzClE3/hcfnaavVVuty3Lo0MX5pqv 3U+rTcIY3axr39UsYalk =eCDJ -----END PGP SIGNATURE----- --en9/O5YN3eJ0yPaf--