lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 May 2020 18:43:48 -0600
From:   "Jason A. Donenfeld" <>
To:     Linus Torvalds <>
Cc:     Linux Kernel Mailing List <>,
        Linux Kbuild mailing list <>,
        "the arch/x86 maintainers" <>,
        stable <>, "H.J. Lu" <>,
        Peter Zijlstra <>,
        Jakub Jelinek <>,
        Oleksandr Natalenko <>,
        Arnd Bergmann <>,
        Andrew Morton <>,
        David Laight <>,
        Masahiro Yamada <>
Subject: Re: [PATCH v2] Kconfig: default to CC_OPTIMIZE_FOR_PERFORMANCE_O3 for
 gcc >= 10

On Mon, May 11, 2020 at 6:05 PM Linus Torvalds
<> wrote:
> There's a reason -O3 isn't even offered as an option.
> Maybe things have changed, and maybe they've improved. But I'd like to
> see actual numbers for something like this.
> Not inlining as aggressively is not necessarily a bad thing. It can
> be, of course. But I've actually also done gcc bugreports about gcc
> inlining too much, and generating _worse_ code as a result (ie
> inlinging things that were behind an "if (unlikely())" test, and
> causing the likely path to grow a stack fram and stack spills as a
> result).
> So just "O3 inlines more" is not a valid argument.

Alright. It might be possible to produce some benchmarks, and then
isolate the precise inlining parameter that makes the difference, and
include that for gcc-10. But you made a compelling argument in that
old gcc bug report about not going down the finicky rabbit hole of gcc
inlining switches that seem to change meaning between releases, which
is persuasive.

The other possibility would be if -O3 actually isn't bad like it used
to be and the codegen is markedly better, alongside some numbers to
back it up. I'm not presently making that argument and don't have
those numbers, but perhaps others who were interested in this patch
for other reasons do have strong arguments there and want to chime in.
Otherwise, no problem dropping this.

Powered by blists - more mailing lists