Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp108467imu; Wed, 7 Nov 2018 13:51:40 -0800 (PST) X-Google-Smtp-Source: AJdET5fW+dV7ZLJsToKcMPhx65i7YjRKKvCOFuvwxBBcFKdKKSJ0v5BjqQab4S0E5amvtnJ0NZRG X-Received: by 2002:a17:902:b789:: with SMTP id e9-v6mr2006326pls.338.1541627500789; Wed, 07 Nov 2018 13:51:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541627500; cv=none; d=google.com; s=arc-20160816; b=JubDzVNQXcK/sQtT5S9gUcG2ZZUkm+KfPOmVQOpH76PbeguIcDCluVozo6haIdgfWT EO5MWGCdFvjacc+2Oy09Fn0aonc+IgO+7jdLev5dFdSityg6gbQVwXDDxu8JLACI9KOt F7W5Toea+W8el16TZalJtsdn27xlMQ8oG/tprqen/jbYBDf+ctiFbFxZavNh3fuz5+FB 8zp7FISxVdwSgMpN9Wh+aXIORQisMnACoIjHCmroqaYNexglRhj4M3C13+qQkC0zyiah SmwJBGvowW6vg6RFx4XWk1pEr+32AmoJBmY8Nx229XGc2bUj1OWwv2RQqlW12GudVava mX2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date; bh=+DJvH/a911G/gKgK4uGr9thGo8tenR77gcSwX3nXPJI=; b=STczg5prqKLOcOCmHqd/kQs8hqQS+RYtc3rPuixHRzw7Wgh90MMKhf2HxDd8BIkDNW HPB34I+ppjKu2p03l27yCJDcm5Zg+nMcfM1YPOEOw02pQnvi4SLZRwV0+PR8KjVqFssl wDRN7BNpzI+1Vc0p6C/k2eKwht/dFIRWcLX2BGSvjUNuQHDje1FxfCCHcmVEgyUsiek/ miO+B6fbVy/l3AFy3jeUqMEKRhcU4g/r3o55SKj0z7KD/Wp+qwUFlGALfSMRrZetcWvO FBwI+K2GeSTbugnS1O194hCfsbO++fDuYUi71/PC0FOrFrWzKeXhi0XP/vA70cz/7Q6J ejBQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 11-v6si1883316pfx.102.2018.11.07.13.51.25; Wed, 07 Nov 2018 13:51:40 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727212AbeKHHXV convert rfc822-to-8bit (ORCPT + 99 others); Thu, 8 Nov 2018 02:23:21 -0500 Received: from terminus.zytor.com ([198.137.202.136]:46247 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726841AbeKHHXV (ORCPT ); Thu, 8 Nov 2018 02:23:21 -0500 Received: from wld62.hos.anvin.org (c-24-5-245-234.hsd1.ca.comcast.net [24.5.245.234] (may be forged)) (authenticated bits=0) by mail.zytor.com (8.15.2/8.15.2) with ESMTPSA id wA7LoawS1655004 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 7 Nov 2018 13:50:36 -0800 Date: Wed, 07 Nov 2018 13:50:28 -0800 User-Agent: K-9 Mail for Android In-Reply-To: <7bc80811-8ab3-d26a-6fb3-b7aeebcfce43@deltatee.com> References: <20181003213100.189959-1-namit@vmware.com> <20181003213100.189959-3-namit@vmware.com> <89262174-6f15-6116-e67f-436f7c1bfe99@deltatee.com> <6651971B-E3AB-4CDD-868C-2338593F7D83@vmware.com> <192946CF-8543-4CF5-B2A3-93674FCD07E2@vmware.com> <7bc80811-8ab3-d26a-6fb3-b7aeebcfce43@deltatee.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [PATCH v9 02/10] Makefile: Prepare for using macros for inline asm To: Logan Gunthorpe , Nadav Amit , Ingo Molnar CC: LKML , X86 ML , Sam Ravnborg , Michal Marek , Thomas Gleixner , Linux Kbuild mailing list , Stephen Bates From: hpa@zytor.com Message-ID: <85B77A64-5FF3-4B82-8A07-E045E259C985@zytor.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On November 7, 2018 1:43:39 PM PST, Logan Gunthorpe wrote: > > >On 2018-11-07 11:56 a.m., Nadav Amit wrote: >> HPA indicated more than once that this is wrong (and that was indeed >my >> initial solution), since it is not guaranteed that the compiler would >put >> the macro assembly before its use. > >Hmm, that's very unfortunate. I don't really understand why the >compiler >would not put the macro assembly in the same order as it appears in the >code and it would be in the correct order there. > >In any case, I've submitted a couple of issues to icecc[1] and >distcc[2] >to see if they have any ideas about supporting this on their sides. > >Thanks, > >Logan > >[1] https://github.com/icecc/icecream/issues/428 >[2] https://github.com/distcc/distcc/issues/312 Apparently gcc will treat them like basic blocks and possibly move them around. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.