[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdkM0F+ajQdLpgUA-WgzhHuV3ydUJskyTeKvY34D62ZRGw@mail.gmail.com>
Date: Mon, 7 Mar 2022 10:19:47 -0800
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Joao Moreira <joao@...rdrivepizza.com>
Cc: Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
hjl.tools@...il.com, jpoimboe@...hat.com,
andrew.cooper3@...rix.com, linux-kernel@...r.kernel.org,
keescook@...omium.org, samitolvanen@...gle.com,
mark.rutland@....com, alyssa.milburn@...el.com, mbenes@...e.cz,
rostedt@...dmis.org, mhiramat@...nel.org,
alexei.starovoitov@...il.com
Subject: Re: [PATCH v3 04/39] x86/ibt: Base IBT bits
On Mon, Mar 7, 2022 at 4:25 AM Joao Moreira <joao@...rdrivepizza.com> wrote:
>
> >
> > Joao will be submitting GCC and Clang bugreports on this shortly.
> >
> Reported both on GCC and Clang:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104816
> https://github.com/llvm/llvm-project/issues/54247
>
> I'm not sure if something should be reported to ClangBuiltLinux, since
> the kernel will be built with -fno-jump-tables anyways.
As long as a bug gets filed; that's what's more important to me.
Doesn't matter if we track it upstream in LLVM's issue tracker or
downstream. Having the record of it in either is what's important to
me. Thanks for filing!
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists