[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK7LNATvGykFY10mOXez84zPV_k3snefgS9zymcn2_7k3EMxAg@mail.gmail.com>
Date: Wed, 2 Oct 2019 22:01:51 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Kate Stewart <kstewart@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, Enrico Weigelt <info@...ux.net>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
Allison Randal <allison@...utok.net>,
Russell King <linux@...linux.org.uk>,
Stefan Agner <stefan@...er.ch>,
LKML <linux-kernel@...r.kernel.org>,
Russell King <rmk+kernel@...linux.org.uk>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Olof Johansson <olof@...om.net>,
Thomas Gleixner <tglx@...utronix.de>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Subject: Re: [PATCH v2] ARM: add __always_inline to functions called from __get_user_check()
Hi Nick,
On Wed, Oct 2, 2019 at 2:04 AM Nick Desaulniers <ndesaulniers@...gle.com> wrote:
> > Since that commit, all architectures can enable CONFIG_OPTIMIZE_INLINING.
> > So, __always_inline is now the only guaranteed way of forcible inlining.
>
> No, the C preprocessor is the only guaranteed way of inlining.
I do not think this is fatal if I understood this correctly:
https://lore.kernel.org/patchwork/patch/1122097/#1331784
For GCC, we at least get a warning if a function with
__always_inline is not inlined.
I am fine with adding -Werror=attributes to the top Makefile
(unless we have unpleasant side-effects).
You filed the bug for Clang, and hopefully it will be OK
in the future releases?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists