[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200916184804.GS2643@zn.tnic>
Date: Wed, 16 Sep 2020 20:48:04 +0200
From: Borislav Petkov <bp@...en8.de>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Arvind Sankar <nivedita@...m.mit.edu>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Rong Chen <rong.a.chen@...el.com>,
kernel test robot <lkp@...el.com>,
"Li, Philip" <philip.li@...el.com>, x86-ml <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Marco Elver <elver@...gle.com>
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING
e6eb15c9ba3165698488ae5c34920eea20eaa38e
On Wed, Sep 16, 2020 at 11:28:26AM -0700, Nick Desaulniers wrote:
> pt. 3 https://nickdesaulniers.github.io/blog/2014/04/18/lets-write-some-x86-64/
/me adds to the read list.
> ...2014, jesus...
>
> "But you never can tell exactly what the compiler is doing. It doesn’t
> always come out the way you want. Like a dusty pane or warped mirror."
Fun quote that. The rest is also very entertaining...
> Seems I'd learn more about that than I'd could have ever envisioned...
Thank <Deity> there's inline asm. This is also why we don't trust
compilers, not even when using builtins. :-P
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists