[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdmVTh8Erha=e97RUp4w-LOq==gV2wyj_0vi176_ZrhTGQ@mail.gmail.com>
Date: Tue, 15 Sep 2020 11:04:45 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Rong Chen <rong.a.chen@...el.com>,
"Li, Philip" <philip.li@...el.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
kernel test robot <lkp@...el.com>, x86-ml <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e
On Tue, Sep 15, 2020 at 11:01 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Tue, Sep 15, 2020 at 10:41:24AM -0700, Nick Desaulniers wrote:
> > We want them finding bugs in unreleased versions of the compiler,
> > before those bugs in ship in release. This is a good thing.
>
> The bug report should probably say that compiler used is an unreleased
> one so that I can prioritize better.
That's not unreasonable. Calling attention to W=1, randconfig, or
unreleased compiler would help. I tend to deprioritize the first two.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists