Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753352AbdCPTHI (ORCPT ); Thu, 16 Mar 2017 15:07:08 -0400 Received: from mail.kernel.org ([198.145.29.136]:38372 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103AbdCPTHH (ORCPT ); Thu, 16 Mar 2017 15:07:07 -0400 Date: Thu, 16 Mar 2017 15:06:48 -0400 From: Steven Rostedt To: Josh Poimboeuf Cc: x86@kernel.org, Andy Lutomirski , Pavel Machek , kernel list , Ingo Molnar , Andrew Lutomirski , Borislav Petkov , Brian Gerst , Denys Vlasenko , Peter Anvin , Peter Zijlstra , Thomas Gleixner , Linus Torvalds Subject: Re: [PATCH] x86: mostly disable '-maccumulate-outgoing-args' Message-ID: <20170316150648.2375e1e5@gandalf.local.home> In-Reply-To: <20170316183635.wlwavbwsgkyjyjcw@treble> References: <20170307173821.yknj5htr7plgdwxv@treble> <20170307182855.262ezbon2pm67qfd@treble> <20170308173703.2h57rsltma3smbcm@treble> <20170308212959.ctb2ktqkg5l6r2xj@treble> <20170316154208.6c3mm6qjus3qtr6w@treble> <20170316133201.16b9a73a@gandalf.local.home> <20170316183635.wlwavbwsgkyjyjcw@treble> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3227 Lines: 91 On Thu, 16 Mar 2017 13:36:35 -0500 Josh Poimboeuf wrote: > On Thu, Mar 16, 2017 at 01:32:01PM -0400, Steven Rostedt wrote: > > On Thu, 16 Mar 2017 10:42:08 -0500 > > Josh Poimboeuf wrote: > > > > > Signed-off-by: Josh Poimboeuf > > > --- > > > arch/x86/Makefile | 29 +++++++++++++++++++++++++---- > > > arch/x86/Makefile_32.cpu | 18 ------------------ > > > arch/x86/kernel/ftrace.c | 6 ++++++ > > > scripts/Kbuild.include | 4 ++++ > > > 4 files changed, 35 insertions(+), 22 deletions(-) > > > > > > diff --git a/arch/x86/Makefile b/arch/x86/Makefile > > > index 2d44933..fa45989b 100644 > > > --- a/arch/x86/Makefile > > > +++ b/arch/x86/Makefile > > > @@ -120,10 +120,6 @@ else > > > # -funit-at-a-time shrinks the kernel .text considerably > > > # unfortunately it makes reading oopses harder. > > > KBUILD_CFLAGS += $(call cc-option,-funit-at-a-time) > > > - > > > - # this works around some issues with generating unwind tables in older gccs > > > - # newer gccs do it by default > > > - KBUILD_CFLAGS += $(call cc-option,-maccumulate-outgoing-args) > > > endif > > > > > > ifdef CONFIG_X86_X32 > > > @@ -147,6 +143,31 @@ ifeq ($(CONFIG_KMEMCHECK),y) > > > KBUILD_CFLAGS += $(call cc-option,-fno-builtin-memcpy) > > > endif > > > > > > +# If the function graph tracer is used with mcount instead of fentry, > > > +# '-maccumulate-outgoing-args' is needed to prevent gcc bug > > > > "to prevent a gcc bug" > > It was > > "to prevent gcc bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42109" > > where "gcc bug" was an adjective and the URL was a noun. But yeah, > that's kind of confusing, and the line wrap made it more so. Maybe I'll > change it to > > "to prevent a gcc bug (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42109)" Hmm, "the" would have made it work too. > > and a similar change for the jump label bug comment. > > > > +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42109 > > > +ifdef CONFIG_FUNCTION_GRAPH_TRACER > > > + ifndef CONFIG_HAVE_FENTRY > > > + ACCUMULATE_OUTGOING_ARGS := 1 > > > + else > > > + ifeq ($(call cc-option, -mfentry),) > > > > Hmm, the blank entry makes me nervous. I wonder if it would be better > > if we had ifneq ($(call cc-option-yn, -mfentry),y) > > > > Unfortunately, there's one of each in the existing kernel, so there is > > really no precedence. > > Either way seems fine. I'll go with your suggested change. > > > > + ACCUMULATE_OUTGOING_ARGS := 1 > > > + endif > > > + endif > > > +endif > > > + > > > +# Jump labels need '-maccumulate-outgoing-args' for gcc < 4.5.2 to prevent > > > > Can we make a test instead? I hate testing versions, and things get > > backported all the time. We usually like to have a test case instead of > > relying on versions. Not to mention, a newer gcc may one day break. > > Tests are generally better, but I'm not sure how to test for this > cleanly. The test is rather big for embedding in a makefile: > > https://gcc.gnu.org/bugzilla/attachment.cgi?id=22199 > > Any ideas? > I'd reply but I see you figured it out yourself. -- Steve