Received: by 10.213.65.68 with SMTP id h4csp2858357imn; Mon, 2 Apr 2018 15:39:45 -0700 (PDT) X-Google-Smtp-Source: AIpwx48sa2Jawjme2z+uXlOcjlbGFwwnHRCwmKLce3309zTa+OspCCcbZeBrsWWpre331osXMU/r X-Received: by 10.101.74.82 with SMTP id a18mr7429117pgu.312.1522708785753; Mon, 02 Apr 2018 15:39:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522708785; cv=none; d=google.com; s=arc-20160816; b=kIyoVYyRXblARAjltLt1b7LX+k+OxRO5ipMrJzmrS3RtQgPRlMwubZ9gajG1ATdow6 3XWs/ljOkeAujJ0N1dFZjp29IIfSR90pVt0Cxv8za5aXjuCZiaZSmVofpjRhcd71GYMC CzWOSbDnjT2vRm4zjdMG6fLH/XzEBI+ZZ2D2uqo8w7mq3Lvd8AP+YObVAwNHaaY4iQCG kh4ZERcgbQOJ5+kIHiSaK7smHDSgCx2N3IaYoTeVvIyc5jrQnHkAfnIv2MCOaqg74c14 c2gwmeV/tmMr7pNncqZdvgLtodAWcMTTTyBDI8gtFj7DWCU255zpaMzJN/JYTpgrmJEH 33Sg== 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:arc-authentication-results; bh=mWoDxO0pJPUTS3KMXzUh/m4XDiztfwTqv6AFAlLZHf8=; b=HprjZaEUV7Vn7AAd2cAH0okqkByF+0WmDv0zbyNVm17CMYD+3XwpRFq8AownchPO6n iAk2+dkpJszy9UC2BKxg7Gx3F2m0Vhf0GYZ1q13cSmCFnfcfgfc5SQ5+TAf5nxMTGul6 OY3KmEmVdG9F8fOFJN+vB2/dHd4abujyE+INCl1mTtXzOxHxYQUlMeQnJ3aTLmFiVpXD 5MirouZa5A3pkSKH4jVL+xb2XjfN3L77VDv220QakYSt+c7c0FukOIyB1zsYNPibeuoG FZKoyQoUNAzz3S7MtqAEMPnLoM+xUaybkzJTwKSWLzMkFLp/PFX0XZ2T6TQxvLX9NS8s b0HQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=ab1B2PAC; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t2si851422pgb.338.2018.04.02.15.39.31; Mon, 02 Apr 2018 15:39:45 -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=pass header.i=@chromium.org header.s=google header.b=ab1B2PAC; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754593AbeDBWiY (ORCPT + 99 others); Mon, 2 Apr 2018 18:38:24 -0400 Received: from mail-pl0-f66.google.com ([209.85.160.66]:43042 "EHLO mail-pl0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754526AbeDBWiX (ORCPT ); Mon, 2 Apr 2018 18:38:23 -0400 Received: by mail-pl0-f66.google.com with SMTP id c21-v6so2485820plz.10 for ; Mon, 02 Apr 2018 15:38:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=mWoDxO0pJPUTS3KMXzUh/m4XDiztfwTqv6AFAlLZHf8=; b=ab1B2PACCfHZqxZNoKbJIbNevD5TydauRYZbfAq9qmbkB+IjbuyyMpRJ3ZH+KAErVY Wx0AUZrS2OKh4ncKjpRVjgWlYMmdHaoBnCLyOCJ6HhjpjjoosfVv/loEkgcHdz/pDRDQ YB/JSuzLqRvg4Y3ztYWv67USheSQ/vUYG4D7o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=mWoDxO0pJPUTS3KMXzUh/m4XDiztfwTqv6AFAlLZHf8=; b=R0/xN1c57vymel2Qz8DamTN+B5C/E6oE+YvtFPEu/RysQ4c8N1GAvWc+YTBDKQv8CD 1zqQe51KtbgJz2EJibZ5S9REuwCLeoohx7q2cZSP9FeFVP4nFDF1RHmuvpffFPuvtoLu tSdeqfwQhMQO+1jCQSsLLWSHNSq7/eTZaqQXL8VvKmysdCSrHIimMvj3b/qASs4L8PIH hwIzt0OnmG/rr4D1xhbdYk0n4hC5nGiyEh7q4kQ92OUgTDxYfv9i+YL2v1bLSVnyKNH7 Kh7LVvOypomQn5MFDGT2xWIrnwgEUrhHMpKg72SBSKZq1tln84nK798z4v9G2z8UqUpm kcnA== X-Gm-Message-State: AElRT7EcZpFUNiwe25BVxdMVXxzJHdF0snQD4LOXfIglGqylcnYvlGwK 2E8vL0OeGGWVRhU/L7KjyRFCSQ== X-Received: by 10.99.95.75 with SMTP id t72mr7383607pgb.411.1522708703004; Mon, 02 Apr 2018 15:38:23 -0700 (PDT) Received: from localhost ([2620:0:1000:1501:8e2d:4727:1211:622]) by smtp.gmail.com with ESMTPSA id s4sm2144283pfm.35.2018.04.02.15.38.21 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Apr 2018 15:38:22 -0700 (PDT) Date: Mon, 2 Apr 2018 15:38:21 -0700 From: Matthias Kaehlcke To: Linus Torvalds Cc: Ingo Molnar , Linux Kernel Mailing List , Thomas Gleixner , Peter Zijlstra , Andrew Morton , James Y Knight , Chandler Carruth , Stephen Hines , Nick Desaulniers , Kees Cook , Greg Kroah-Hartman Subject: Re: [GIT PULL] x86/build changes for v4.17 Message-ID: <20180402223821.GC87376@google.com> References: <20180402095033.nfzcrmxvpm46dhbl@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org El Mon, Apr 02, 2018 at 02:44:48PM -0700 Linus Torvalds ha dit: > On Mon, Apr 2, 2018 at 2:50 AM, Ingo Molnar wrote: > > > > The biggest change is the forcing of asm-goto support on x86, which effectively > > increases the GCC minimum supported version to gcc-4.5 (on x86). > > So my biggest worry isn't gcc-4.5 (anybody who hasn't updated deserves > to be forced, or can stay with old kernels). > > No, my biggest worry is clang. What's the status there? I know there is work in progress for asm-goto in clang, but I don't know the details or an ETA. Some folks in cc might have more information. > I've pulled this, and honestly, the disaster with > -fmerge-all-constants makes me think that clang isn't that good a > compiler choice anyway, but it's sad if this undoes a lot of clang > work just because of the worries about Spectre and mis-speculated > branches. It would indeed be very unfortunate to loose clang support again, now that it just got added after years of joint efforts from different people. And this wasn't exclusively kernel work, in my experience over the past year the LLVM community was very open to adopt/implement changes needed to build the kernel without ugly hacks. It's still not a perfect world, but I think LLVM folks deserve some credit. Couldn't we just raise the minimum gcc version without enforcing asm-goto for clang (yet)? This would give almost everybody the desired extra protection, and give clang some slack to implement asm goto.