From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
x86@kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/2] Add CONFIG_READABLE_ASM
Date: Thu, 12 Apr 2012 21:42:02 +0200 [thread overview]
Message-ID: <CAMuHMdXi6oOPz-9vV7ccdpVnoED3ayK1sT0bs6nZrcGzCw94Ew@mail.gmail.com> (raw)
In-Reply-To: <4F872ED8.1060608@kernel.org>
On Thu, Apr 12, 2012 at 21:36, H. Peter Anvin <hpa@kernel.org> wrote:
> On 04/12/2012 12:08 PM, Geert Uytterhoeven wrote:
>> On Wed, Mar 28, 2012 at 20:51, Andi Kleen <andi@firstfloor.org> wrote:
>>> +ifdef CONFIG_READABLE_ASM
>>> +# Disable optimizations that make assembler listings hard to read.
>>> +# reorder blocks reorders the control in the function
>>> +# ipa clone creates specialized cloned functions
>>> +# partial inlining inlines only parts of functions
>>> +KBUILD_CFLAGS += $(call cc-option,-fno-reorder-blocks,) \
>>> + $(call cc-option,-fno-ipa-cp-clone,) \
>>> + $(call cc-option,-fno-partial-inlining)
>>> +endif
>>
>> This (now in linux-next) causes m68k/allmodconfig to fail for me:
>>
>> CHK include/linux/version.h
>> CHK include/generated/utsrelease.h
>> CC kernel/bounds.s
>> cc1: error: unrecognized command line option "-fno-ipa-cp-clone"
>>
>> Somehow, "$(call cc-option,-fno-ipa-cp-clone,)" doesn't detect that my
>> toolchain (gcc version 4.1.2 20061115 (prerelease) (Ubuntu 4.1.1-21))
>> doesn't support this option.
>>
>> I tried playing with the trailing comma (why do the first 2 tests have it,
>> and the 3rd one doesn't?), but that didn't make a difference.
>>
>> linux-next builds (using a newer toolchain) don't show this.
>>
>
> Sounds like the fundamental action item is to find out what makes
> cc-option not work.
FWIW, it did detect that:
- -fno-reorder-blocks is supported,
- -fno-partial-inlining is not supported.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2012-04-12 19:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 18:51 [PATCH 1/2] x86: Use -mno-avx when available Andi Kleen
2012-03-28 18:51 ` [PATCH 2/2] Add CONFIG_READABLE_ASM Andi Kleen
2012-03-30 17:41 ` [tip:x86/cleanups] debug: " tip-bot for Andi Kleen
2012-04-12 19:08 ` [PATCH 2/2] " Geert Uytterhoeven
2012-04-12 19:36 ` H. Peter Anvin
2012-04-12 19:42 ` Geert Uytterhoeven [this message]
2012-04-12 19:40 ` Sam Ravnborg
2012-04-12 19:47 ` Geert Uytterhoeven
2012-04-12 19:52 ` Sam Ravnborg
2012-04-12 19:57 ` Andi Kleen
2012-04-12 20:07 ` Sam Ravnborg
2012-04-12 20:17 ` Geert Uytterhoeven
2012-04-12 20:35 ` Sam Ravnborg
2012-05-08 19:36 ` Geert Uytterhoeven
2012-05-12 20:23 ` Geert Uytterhoeven
2012-05-12 20:25 ` Sam Ravnborg
2012-03-30 17:16 ` [tip:x86/urgent] x86: Use -mno-avx when available tip-bot for Andi Kleen
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=CAMuHMdXi6oOPz-9vV7ccdpVnoED3ayK1sT0bs6nZrcGzCw94Ew@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).