From: Arnd Bergmann <arnd@arndb.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Changbin Du <changbin.du@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Hans de Goede <hdegoede@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: Tree for Oct 31 (vboxguest)
Date: Fri, 2 Nov 2018 16:54:25 +0100 [thread overview]
Message-ID: <CAK8P3a1w8p8OC-9_0mtMUxEojvyVfXvF8Ka4J7TnoyZ=gr2Fow@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQbBG=KV5Q8o5-JiNCswuse94jECoqT+T+UEY7bLCRPNw@mail.gmail.com>
On 11/2/18, Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> On Thu, Nov 1, 2018 at 11:32 PM Changbin Du <changbin.du@gmail.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
next prev parent reply other threads:[~2018-11-02 15:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 3:59 linux-next: Tree for Oct 31 Stephen Rothwell
2018-10-31 15:51 ` linux-next: Tree for Oct 31 (vboxguest) Randy Dunlap
2018-10-31 16:50 ` Hans de Goede
2018-10-31 19:06 ` Randy Dunlap
2018-10-31 21:41 ` Arnd Bergmann
2018-10-31 21:45 ` Randy Dunlap
2018-11-01 3:32 ` Masahiro Yamada
2018-11-01 14:29 ` Changbin Du
2018-11-02 8:25 ` Masahiro Yamada
2018-11-02 15:54 ` Arnd Bergmann [this message]
2018-11-02 23:59 ` Changbin Du
2018-11-04 2:43 ` Masahiro Yamada
2018-11-04 23:38 ` Changbin Du
2018-11-05 3:00 ` Masahiro Yamada
2018-11-02 23:59 ` Changbin Du
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='CAK8P3a1w8p8OC-9_0mtMUxEojvyVfXvF8Ka4J7TnoyZ=gr2Fow@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=changbin.du@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=yamada.masahiro@socionext.com \
/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).