[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjnuMD091mNbY=fRm-qFyhMjbtfiwkAFKyFehyR8bPB5A@mail.gmail.com>
Date: Thu, 31 Mar 2022 11:16:53 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Aurelien Jarno <aurelien@...el32.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Kito Cheng <kito.cheng@...il.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
"open list:RISC-V ARCHITECTURE" <linux-riscv@...ts.infradead.org>,
Sparse Mailing-list <linux-sparse@...r.kernel.org>,
ukl@...gutronix.de,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Subject: Re: [PATCH] riscv: fix build with binutils 2.38
On Thu, Mar 31, 2022 at 3:51 AM Marc Kleine-Budde <mkl@...gutronix.de> wrote:
>
> Cc += linux-sparse, Uwe, Luc Van Oostenryck
>
> tl;dr:
>
> A recent change in the kernel regarding the riscv -march handling breaks
> current sparse.
Gaah. Normally sparse doesn't even look at the -march flag, but for
riscv it does, because it's meaningful for the predefined macros.
Maybe that 'die()' shouldn't be so fatal. And maybe add a few more
extensions (but ignore them) to the parsing.
Something ENTIRELY UNTESTED like the attached.
Linus
View attachment "patch.diff" of type "text/x-patch" (1074 bytes)
Powered by blists - more mailing lists