[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03B86732-8D0B-40A7-B09C-5823104E631F@vmware.com>
Date: Wed, 16 May 2018 04:30:19 +0000
From: Nadav Amit <namit@...are.com>
To: Josh Poimboeuf <jpoimboe@...hat.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Alok Kataria <akataria@...are.com>,
Christopher Li <sparse@...isli.org>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Jan Beulich <JBeulich@...e.com>,
Jonathan Corbet <corbet@....net>,
Juergen Gross <jgross@...e.com>,
Kees Cook <keescook@...omium.org>,
"linux-sparse@...r.kernel.org" <linux-sparse@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Randy Dunlap <rdunlap@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [RFC 0/8] Improving compiler inlining decisions
Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> On Tue, May 15, 2018 at 07:11:07AM -0700, Nadav Amit wrote:
>> This patch-set deals with an interesting yet stupid problem: code that
>> does not get inlined despite its simplicity.
>
> I got the 0/8 patch twice, and didn't get the 1/8 patch. Was there an
> issue with the sending of the patches?
Strange. I am not sure why it happened. Anyhow 1/8 is available here:
https://lkml.org/lkml/2018/5/15/961 . I will forward it to you.
Thanks,
Nadav
Powered by blists - more mailing lists