From owner-freebsd-arch@FreeBSD.ORG Mon Jan 14 21:22:17 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 3BA981D5; Mon, 14 Jan 2013 21:22:17 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id D844EB35; Mon, 14 Jan 2013 21:22:16 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r0ELMF9o019071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Jan 2013 13:22:15 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r0ELMFF4019070; Mon, 14 Jan 2013 13:22:15 -0800 (PST) (envelope-from jmg) Date: Mon, 14 Jan 2013 13:22:15 -0800 From: John-Mark Gurney To: John Baldwin Subject: Re: how long to keep support for gcc on x86? Message-ID: <20130114212215.GV1410@funkthat.com> Mail-Followup-To: John Baldwin , freebsd-arch@freebsd.org, Konstantin Belousov , Adrian Chadd References: <20130112233147.GK1410@funkthat.com> <20130113132402.GR2561@kib.kiev.ua> <201301141110.44165.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201301141110.44165.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 14 Jan 2013 13:22:15 -0800 (PST) Cc: Konstantin Belousov , 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: Mon, 14 Jan 2013 21:22:17 -0000 John Baldwin wrote this message on Mon, Jan 14, 2013 at 11:10 -0500: > On Sunday, January 13, 2013 8:24:02 am Konstantin Belousov wrote: > > 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: > > > > > > > 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. > > > > > > 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. > > It is not but so hard to add new instructions to binutils. I did it recently > for the xsave stuff as well the instructions needed by bhyve. How many > instructions are you talking about (and which ones)? Would adding them to binutils support inline assembly? Though supporting them in gas would be useful tool, but inline assembly would be best (so the compiler can do register allocation optimizations).. The instructions are aesenc, aesenclast, aesdec, aesdeclast.. And if you want to be complete, aeskeygenassist, aesimc, pclmulqdq... Though pclmulqdq isn't currently used... I'm willing to do some of the work and debugging too, just I don't know which files to modify, etc... I couldn't find any good guides on the internet that talks about this.. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."