[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nf2qyNxJ2Z9nypzqUC99-v5+WC_f3o98P-zoMqy+5sLw@mail.gmail.com>
Date: Sat, 9 Feb 2019 12:19:28 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Laura Abbott <labbott@...hat.com>,
Arnd Bergmann <arnd@...db.de>,
Martin Sebor <msebor@....gnu.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Krzysztof Kozlowski <krzk@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
Andrey Konovalov <andreyknvl@...gle.com>,
Kees Cook <keescook@...omium.org>,
Sean Christopherson <sean.j.christopherson@...el.com>,
Jessica Yu <jeyu@...nel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
James Morris <james.morris@...rosoft.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Borislav Petkov <bp@...e.de>, Matt Mullins <mmullins@...com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
WANG Chao <chao.wang@...oud.cn>
Subject: Re: [PATCH 0/3] Clean the new GCC 9 -Wmissing-attributes warnings
On Sat, Feb 9, 2019 at 11:44 AM Ard Biesheuvel
<ard.biesheuvel@...aro.org> wrote:
>
> On Sat, 9 Feb 2019 at 01:09, Miguel Ojeda
> <miguel.ojeda.sandonis@...il.com> wrote:
> >
> > The upcoming GCC 9 release extends the -Wmissing-attributes warnings
> > (enabled by -Wall) to C and aliases: it warns when particular function
> > attributes are missing in the aliases but not in their target, e.g.:
> >
> > void __cold f(void) {}
>
> Apologies if I missed any discussions on this topic, but I would argue
> that 'cold' is not an attribute that has to be applied to the function
> pointer as well as each of its targets, since it basically decides the
> placement in the binary, and it doesn't affect the nature of the code
> being referenced.
It also affects the optimizer in two different ways AFAIK:
* For the function itself, it gets optimized for size instead of speed.
* For callers, the paths that lead to the calls are treated as unlikely.
So GCC reports it because you would be (likely) missing the
optimizations you expected if you are using the alias instead of the
target.
In our case in patch 3, we do not want the optimization for callers,
which is why we don't mark the extern declaration as __cold (see the
commit message).
Cheers,
Miguel
Powered by blists - more mailing lists