From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: LEROY Christophe <christophe.leroy@c-s.fr>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arch <linux-arch@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Dave Hansen <dave@sr71.net>,
"the arch/x86 maintainers" <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips@vger.kernel.org, Paul Burton <paul.burton@mips.com>,
Ingo Molnar <mingo@redhat.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] compiler: allow all arches to enable CONFIG_OPTIMIZE_INLINING
Date: Mon, 25 Mar 2019 15:44:06 +0900 [thread overview]
Message-ID: <CAK7LNAQGifytZRQXcqma9VuvQPfL2w8NjzLRt7CxzFgvaMhyRw@mail.gmail.com> (raw)
In-Reply-To: <20190323092640.Horde.2lm4u26aZox5ialxuIRcYw2@messagerie.si.c-s.fr>
Hi Christophe,
On Sat, Mar 23, 2019 at 5:27 PM LEROY Christophe
<christophe.leroy@c-s.fr> wrote:
>
> Arnd Bergmann <arnd@arndb.de> a écrit :
>
> > On Wed, Mar 20, 2019 at 10:41 AM Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> I've added your patch to my randconfig test setup and will let you
> >> know if I see anything noticeable. I'm currently testing clang-arm32,
> >> clang-arm64 and gcc-x86.
> >
> > This is the only additional bug that has come up so far:
> >
> > `.exit.text' referenced in section `.alt.smp.init' of
> > drivers/char/ipmi/ipmi_msghandler.o: defined in discarded section
> > `exit.text' of drivers/char/ipmi/ipmi_msghandler.o
>
> Wouldn't it be useful to activate -Winline gcc warning to ease finding
> out problematic usage of inline keyword ?
Yes, it is useful to find out
which function is causing the error.
Thanks for the tip.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2019-03-25 6:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 6:20 [PATCH] compiler: allow all arches to enable CONFIG_OPTIMIZE_INLINING Masahiro Yamada
2019-03-20 6:40 ` Masahiro Yamada
2019-03-20 9:38 ` Arnd Bergmann
2019-03-20 10:18 ` Masahiro Yamada
2019-03-20 13:04 ` Arnd Bergmann
2019-03-25 6:04 ` Masahiro Yamada
2019-03-20 9:41 ` Arnd Bergmann
2019-03-20 13:34 ` Arnd Bergmann
2019-03-23 8:26 ` LEROY Christophe
2019-03-25 6:44 ` Masahiro Yamada [this message]
2019-03-26 6:02 ` Christophe Leroy
2019-04-23 3:26 ` Masahiro Yamada
2019-03-25 6:10 ` Masahiro Yamada
2019-03-25 6:12 ` Masahiro Yamada
2019-03-25 7:32 ` Arnd Bergmann
2019-03-25 7:54 ` Masahiro Yamada
2019-03-25 10:25 ` Arnd Bergmann
2019-03-25 10:27 ` Arnd Bergmann
2019-03-21 8:01 ` Heiko Carstens
2019-03-25 6:41 ` Masahiro Yamada
2019-03-23 8:37 ` LEROY Christophe
2019-04-18 13:20 ` Ingo Molnar
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=CAK7LNAQGifytZRQXcqma9VuvQPfL2w8NjzLRt7CxzFgvaMhyRw@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@c-s.fr \
--cc=dave@sr71.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=paul.burton@mips.com \
--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).