Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp571614imm; Wed, 10 Oct 2018 00:23:20 -0700 (PDT) X-Google-Smtp-Source: ACcGV62ay+k4UjkjLLTvQ5ZBirrH1N3qJGIhDsOZWFlC8vmEkJyEuORuVqm7kksGvkd4szneb8sM X-Received: by 2002:aa7:8252:: with SMTP id e18-v6mr29184937pfn.164.1539156200259; Wed, 10 Oct 2018 00:23:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539156200; cv=none; d=google.com; s=arc-20160816; b=R9EjXthEapEnxCpn3cYued7WzeeFCxTl3NdP/7rPjfBEEWHZM0pXW/kjfArN30J4/5 K7uPsPLuIGV3s91Ygcew2qdQ8fzd1IONsZNFTyvcxdxbaMcHqDTQ3ha1Z30QgmgurdI6 93kD+Z4JAvdYkN9kez+ws7vimVnk+ctLatbXup0V8iGu0gLumwMn27duA6l8JiLUDrK4 YRqMoiP2wMAl1Zt6I7l6AyIONQrnVm1gm+YgQCyQQJN3Jqte5CziO98qdbqIbiBJJWWH 61C4IVD1je8hMzF3PZJOknZXnos9Rrl1LERqGkWnyT/gP8V1qXxr51lqknXKDljbgoA+ aqUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=yPfb4YFX/q8A1De8WDJ42fxiXtE8tETkaUjFqrJDi5Y=; b=XWBFe7lITOCHktLfdxf0fzaBA3XmHUT8Jvf8sPRzH/MnsR2eoAoZjc540/k/IaQKa+ BC6Vl2pfxKmuhFDc+nnJe+Pie55PGLMGihihXcpMzVz2N10nHjifLyGqfh0mjBsqhQF3 N/SNdthUtwbj2OhH/q29uV+JposRVtqK/WHS3wrBYJ76YQqW1dC9RcOj5PYabACWeWdo KtT+ZcJYutCb6Ercr6Z7vR7c9cGEMiTxsfsQXi24aBL/lDdwmvh9cWsCxCO5c4MWcOMd FsUXbaTaC1MdHZExXoWrgQ1tdS8fR8PfCJ9w/+c0GOq5iY466/0HlGTQe+c64gxVCgwQ Zxhg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=piL+NEqa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m2-v6si12968277pgv.440.2018.10.10.00.23.05; Wed, 10 Oct 2018 00:23:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=piL+NEqa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726664AbeJJOnf (ORCPT + 99 others); Wed, 10 Oct 2018 10:43:35 -0400 Received: from mail-wr1-f65.google.com ([209.85.221.65]:35302 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726607AbeJJOnf (ORCPT ); Wed, 10 Oct 2018 10:43:35 -0400 Received: by mail-wr1-f65.google.com with SMTP id w5-v6so4446115wrt.2; Wed, 10 Oct 2018 00:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=yPfb4YFX/q8A1De8WDJ42fxiXtE8tETkaUjFqrJDi5Y=; b=piL+NEqaqg6gBXyGHQIaVf1FhFJzuL8VebETWRlP8zfgWHtJpp76q0mSjs50tf7WK/ A3p8qPJEyLxC9SXVhHHYsmtig0ZbFgvdH55x3rxn5IfZ0mAEJ3gJgYYRWyHEDEwEDhSu GTVbXF3eQ7sLFjLP9IOGVw2aIqm4pHqvTYdZNNL+gW/ZkrDDECuJP/LVArUWMBdbwWx+ O/+z/yHzRo+9LhY1Y7LwG1oabEyVyydDcXr3EKNAH8A6iEtSdsucD+UmuwMRwSlx6MrI s3sUHDrgWnAkKMs670zSuCuzRmuuk76Xby179iX0+QxapF05JY5jr8slDShhKSJIEw3B T2mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=yPfb4YFX/q8A1De8WDJ42fxiXtE8tETkaUjFqrJDi5Y=; b=jXobpGZ2HWsV1LeOGq+a4iSAkYgI7hHGr53KbhFT4hZrkHJualPlXJxKV8/s3mH2Dg U36YHeKz/8/QWUI2B6CB1jNYktvZyKWLME/Hbai+PyU9d+aa3MRYP5oKy5zt5d5lSdap pHF8VW2IG/3mFmx/0Ax1VVYJf+wokuOmzFo5eqhtRO/alS8E08Pqt/916e9u4wdamELE gNcBNMCV4/GZKIvXW+ewxzhLWumNlSjYRB0KrlgP8ovBO+ghmazjsle77KIf6l+Uw+A2 1ROOoQ6CH6y3cVRHj+2tGub6IbCj14OIJRCKMHL1NdcjzZB6Ea0ev4OIkDADiDMhn9O/ 68zQ== X-Gm-Message-State: ABuFfojbhVORtelfD+uhdDhs1f8oFud61mKhRKwh58uYdIQLIlNmKBmF LdMUhNCKCXcEuKsKHxAJHrI= X-Received: by 2002:adf:bb02:: with SMTP id r2-v6mr22537206wrg.24.1539156164367; Wed, 10 Oct 2018 00:22:44 -0700 (PDT) Received: from gmail.com (2E8B0CD5.catv.pool.telekom.hu. [46.139.12.213]) by smtp.gmail.com with ESMTPSA id y65-v6sm12725990wmg.40.2018.10.10.00.22.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 10 Oct 2018 00:22:43 -0700 (PDT) Date: Wed, 10 Oct 2018 09:22:40 +0200 From: Ingo Molnar To: Richard Biener Cc: Segher Boessenkool , Michael Matz , Borislav Petkov , gcc@gcc.gnu.org, Nadav Amit , Ingo Molnar , linux-kernel@vger.kernel.org, x86@kernel.org, Masahiro Yamada , Sam Ravnborg , Alok Kataria , Christopher Li , Greg Kroah-Hartman , "H. Peter Anvin" , Jan Beulich , Josh Poimboeuf , Juergen Gross , Kate Stewart , Kees Cook , linux-sparse@vger.kernel.org, Peter Zijlstra , Philippe Ombredanne , Thomas Gleixner , virtualization@lists.linux-foundation.org, Linus Torvalds , Chris Zankel , Max Filippov , linux-xtensa@linux-xtensa.org, Andrew Morton Subject: Re: PROPOSAL: Extend inline asm syntax with size spec Message-ID: <20181010072240.GB103159@gmail.com> References: <20181003213100.189959-1-namit@vmware.com> <20181007091805.GA30687@zn.tnic> <20181007132228.GJ29268@gate.crashing.org> <20181008073128.GL29268@gate.crashing.org> <20181009145330.GT29268@gate.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Richard Biener wrote: > Can kernel folks give this a second and third thought please so we > don't implement sth that in the end won't satisfy you guys? So this basically passes '0 size' to the inliner, which should be better than passing in the explicit size, as we'd inevitably get it wrong in cases. I also like 'size 0' for the reason that we tend to write assembly code and mark it 'inline' if we really think it matters to performance, so making it more likely to be inlined when used within another inline function is a plus as well. Does anyone have any concerns about this? Thanks, Ingo