From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754861AbcFHIAh (ORCPT ); Wed, 8 Jun 2016 04:00:37 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:52617 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751606AbcFHIAg (ORCPT ); Wed, 8 Jun 2016 04:00:36 -0400 Date: Wed, 8 Jun 2016 10:00:29 +0200 From: Peter Zijlstra To: "H. Peter Anvin" Cc: Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Linux Kernel Mailing List , Andy Lutomirski , Borislav Petkov Subject: Re: [PATCH 00/10] x86: use gcc 6+ asm flag output feature Message-ID: <20160608080029.GP30154@twins.programming.kicks-ass.net> References: <1465342269-492350-1-git-send-email-hpa@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1465342269-492350-1-git-send-email-hpa@linux.intel.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 07, 2016 at 04:30:59PM -0700, H. Peter Anvin wrote: > From: "H. Peter Anvin" > > gcc 6+ has the ability to let flags (actually, conditions, which are > specific combinations of flags) to be used directly as asm() outputs. > The syntax for that is "=@cc" where is the same set of > letters that would be used in a j or set instruction > (e.g. "=@ccz" to test the ZF flag.) > > This patchset by itself reduces the size of the x86-64 kernel by > 0.12%, from a baseline of 4.7-rc2 built with gcc 6.1 (first line is > with the patchset, the second one is without): > > text data bss dec hex filename > > 68245656 41004339 20533248 129783243 7bc55cb o.i386-allconfig/vmlinux > 68355716 41008499 20533248 129897463 7be13f7 o.i386-allconfig/vmlinux > > 127384005 129742359 38150144 295276508 11998fdc o.x86_64-allconfig/vmlinux > 127538765 129742295 38150144 295431204 119bec24 o.x86_64-allconfig/vmlinux Very nice! Acked-by: Peter Zijlstra (Intel) Do you happen to know if GCC plans to support other architectures for =@cc ?