[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1w8p8OC-9_0mtMUxEojvyVfXvF8Ka4J7TnoyZ=gr2Fow@mail.gmail.com>
Date: Fri, 2 Nov 2018 16:54:25 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Changbin Du <changbin.du@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Hans de Goede <hdegoede@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: linux-next: Tree for Oct 31 (vboxguest)
On 11/2/18, Masahiro Yamada <yamada.masahiro@...ionext.com> wrote:
> On Thu, Nov 1, 2018 at 11:32 PM Changbin Du <changbin.du@...il.com> wrote:
>> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote:
>
> How about clang?
>
> For clang, -Og might be equivalent to -O1 at this moment, but I am not
> sure.
>
> In my understanding, Clang does not inline functions marked with 'static
> inline'
> for -Og (or -O1) optimization level.
>
> Theoretically, 'inline' keyword is a just hint for the compiler, after all.
I think this means that we cannot build the kernel in that configuration,
at least with CONFIG_OPTIMIZE_INLINING=y. Without that option,
every 'inline' becomes 'always_inline'.
Arnd
Powered by blists - more mailing lists