From: Ingo Molnar <mingo@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: add the flag -fno-reorder-blocks-and-partition
Date: Tue, 15 May 2018 07:33:57 +0200 [thread overview]
Message-ID: <20180515053357.GA18398@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1805150121340.30961@file01.intranet.prod.int.rdu2.redhat.com>
* Mikulas Patocka <mpatocka@redhat.com> wrote:
> GCC 8 turns on -freorder-blocks-and-partition by default, the ORC unwinder
> can't deal with it and it results in a lot of warnings "sibling call from
> callable instruction with modified stack frame". This patch adds the
> -fno-reorder-blocks-and-partition option to KBUILD_CFLAGS.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable@vger.kernel.org
>
> ---
> arch/x86/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> Index: linux-2.6/arch/x86/Makefile
> ===================================================================
> --- linux-2.6.orig/arch/x86/Makefile 2018-05-15 07:19:40.000000000 +0200
> +++ linux-2.6/arch/x86/Makefile 2018-05-15 07:19:40.000000000 +0200
> @@ -59,6 +59,7 @@ endif
> #
> KBUILD_CFLAGS += -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> KBUILD_CFLAGS += $(call cc-option,-mno-avx,)
> +KBUILD_CFLAGS += $(call cc-option,-fno-reorder-blocks-and-partition,)
Could you check whether the latest objtool fixes in -tip:
git git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git master
solves those warnings?
Thanks,
Ingo
next prev parent reply other threads:[~2018-05-15 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 5:23 Mikulas Patocka
2018-05-15 5:33 ` Ingo Molnar [this message]
2018-05-22 0:19 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180515053357.GA18398@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®