Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1216815ybl; Fri, 30 Aug 2019 13:55:41 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9tfYmcVBOjojUPYStfTwtkdl9ROBl+z69NDjdIzzoZSC9ovWNkh93kHmBsRPjuE4+nPd+ X-Received: by 2002:a17:902:12d:: with SMTP id 42mr16855069plb.187.1567198541348; Fri, 30 Aug 2019 13:55:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567198541; cv=none; d=google.com; s=arc-20160816; b=Q57HVhl3la+0uXibR/yPMD8Uc0WLB93jVbSEouJHAqhZxZgPuqyTmS5Nb2QsDEo/YT oht39W+or7trSM5hHMQM0kltjAJyI92zJUeoC59JvMjG5E8VOKOEfafVguPvevUbzYc2 2vCRTDpysTdJD7kSNaL2q2aNLFhY87ve9zC6eGg5IY9ykBC+9UmODBpb6fxlJ8yKyCFo Pc+u1sydQHfviK1vNTPhFuFZJTJcC73RiLUxXKsB23pWnpzOFTRxEN+9Zbcqoiq7qudx Sa/UWqTGathsABoB8tIJoERJDfRgTh+txmzBz30lib9n1JSEKjYkAMhfEIeZHEXP9ufw RLzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=2CVy2kCQ2mXWtQaNrZE0v2BXiv9fAYysPjc4OIAAcWY=; b=k/7LEMIEK8mvx9A1D1XbYWu6uGoC+a93KP9c7THdRIPGfiIoXYumXSP9D2AI9SATQq TZDUjR8kuX7ezkuMsdBfaTWOM4eiD5EuEYZ2rkyQzXaSReDLH6BxsVqmNJTWWS/zLCEU OTkcEg+S2RqQQh2i4Qk+basoJw798QT6QVvd7vvd2fDqUIxYBGaA4YoyR27UKL7w6G38 kZYIbKZN+3o8MY5uh6Usk4aQy/NavDu18dn9/i9GNyU4k8QobjsCr8kkJ6jl+M7PEVwo QX6i77+ZK5Sbom2WqYBxFP+Q1Bqz5KzAcLD4nyi7sh59TNgkd8bX1tQFN6upulupZGVO /Dnw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=UhfqOxHM; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i64si5388146pli.252.2019.08.30.13.55.25; Fri, 30 Aug 2019 13:55:41 -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=@google.com header.s=20161025 header.b=UhfqOxHM; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728094AbfH3Uyi (ORCPT + 99 others); Fri, 30 Aug 2019 16:54:38 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:34865 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727304AbfH3Uyi (ORCPT ); Fri, 30 Aug 2019 16:54:38 -0400 Received: by mail-pg1-f193.google.com with SMTP id n4so4125501pgv.2 for ; Fri, 30 Aug 2019 13:54:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2CVy2kCQ2mXWtQaNrZE0v2BXiv9fAYysPjc4OIAAcWY=; b=UhfqOxHMV3jQk1xxzvo2MP0OgXffqTvi1/n6Lctg168ayE83maKFExtHkHGK5bBAKc LQTKGr2hoMIQ4cc8ZfPZcHcoE0UBuAb5SNAATRwBIti1kBdiFoPvPOAXIYXeWDgPBmyx /fEZ9QGU+wM/ykDw3mJia1XcQ1Yu9GMgqPbXYqMGRQqri7Tf+Iiuj0G3HeZSJrUwAPlv 1Fq24WLpFuL9jRHVzJk4g/NjLBaGISkhLfL9AIsxY5Wdm/RixZu+A4UaS1vO6RYNMkLj 0cqI2pHgwClwRGjxOhwG97tpuYn44UtfsVkC63Dg0dpURoxZ4WUQ457JQq6CTLsnUVpj AQzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2CVy2kCQ2mXWtQaNrZE0v2BXiv9fAYysPjc4OIAAcWY=; b=XTEwQz3401xqte2iOTI8C/QCR/Z1a6s0WYWCvDIx6EGRLhHEyo6fV4xKAoNlOON1EH N2HdR68a0jHQfSDG91aXPRHrvNKteRBUbJgTIQ+BiORTIO+IZY9jOJ1HBc0spYt1evym NMq8WA7zHwtV+szICRPKIE84fRcCvonzBdna612iJ6Xw1zRRpGaZbOP33kfwpfhuPLxy /2LtGNGfYma85B7omvRuPgpGKh9oBDtqPumY3xnAJiQOX8A4AfaQP//cHmcvjZjcgMpf HKo6Jrlmu/N7f4h+1tuInGIKqzzJrZ1sDhiwsjp4QJY3650ll38KpAY24b69zS7jgIrZ sIzA== X-Gm-Message-State: APjAAAVRt/2jBP37+HyiOq8RG08D2UpHyA6TAUf2DdvRX++v9OjKl3Mz HJ3XfU7IvPLMO0LpiqEqIS8dtEQ1s3o3xb2mtX1yYw== X-Received: by 2002:aa7:8085:: with SMTP id v5mr20489464pff.165.1567198477179; Fri, 30 Aug 2019 13:54:37 -0700 (PDT) MIME-Version: 1.0 References: <20190830034304.24259-1-yamada.masahiro@socionext.com> In-Reply-To: <20190830034304.24259-1-yamada.masahiro@socionext.com> From: Nick Desaulniers Date: Fri, 30 Aug 2019 13:54:26 -0700 Message-ID: Subject: Re: [PATCH] compiler: enable CONFIG_OPTIMIZE_INLINING forcibly To: Masahiro Yamada Cc: Andrew Morton , Ingo Molnar , Borislav Petkov , Linus Torvalds , Miguel Ojeda , linux-arch , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 29, 2019 at 8:43 PM Masahiro Yamada wrote: > > Commit 9012d011660e ("compiler: allow all arches to enable > CONFIG_OPTIMIZE_INLINING") allowed all architectures to enable > this option. A couple of build errors were reported by randconfig, > but all of them have been ironed out. > > Towards the goal of removing CONFIG_OPTIMIZE_INLINING entirely > (and it will simplify the 'inline' macro in compiler_types.h), > this commit changes it to always-on option. Going forward, the > compiler will always be allowed to not inline functions marked > 'inline'. > > This is not a problem for x86 since it has been long used by > arch/x86/configs/{x86_64,i386}_defconfig. > > I am keeping the config option just in case any problem crops up for > other architectures. > > The code clean-up will be done after confirming this is solid. > > Signed-off-by: Masahiro Yamada Just saw akpm picked this up, but Acked-by: Nick Desaulniers > --- > > lib/Kconfig.debug | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index 5960e2980a8a..e25493811df8 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -327,7 +327,7 @@ config HEADERS_CHECK > relevant for userspace, say 'Y'. > > config OPTIMIZE_INLINING > - bool "Allow compiler to uninline functions marked 'inline'" > + def_bool y > help > This option determines if the kernel forces gcc to inline the functions > developers have marked 'inline'. Doing so takes away freedom from gcc to > @@ -338,8 +338,6 @@ config OPTIMIZE_INLINING > decision will become the default in the future. Until then this option > is there to test gcc for this. > > - If unsure, say N. > - > config DEBUG_SECTION_MISMATCH > bool "Enable full Section mismatch analysis" > help > -- > 2.17.1 > -- Thanks, ~Nick Desaulniers