[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5140f54-99f2-4d7f-8b53-bd3cd1093727@t-8ch.de>
Date: Fri, 19 May 2023 12:11:00 +0200
From: Thomas Weißschuh <thomas@...ch.de>
To: Willy Tarreau <w@....eu>
Cc: Zhangjin Wu <falcon@...ylab.org>,
Palmer Dabbelt <palmer@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
"Paul E . McKenney" <paulmck@...nel.org>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] tools/nolibc: riscv: Fix up compile error for rv32
Hi Willy,
On 2023-05-19 11:40:30+0200, Willy Tarreau wrote:
> Hi Zhangjin,
>
> On Fri, May 19, 2023 at 01:00:18AM +0800, Zhangjin Wu wrote:
> > Hi, Willy
> >
> > nolibc for riscv is only tested for rv64 currently (see
> > tools/testing/selftests/nolibc/Makefile), this patchset tries to let it
> > compile for rv32, but still not pass the nolibc selftest:
> >
> > * The first patch uses lw/sw instead of ld/sd for rv32 and verse-vice for rv64
> > * This patch may conflict with the stackprotector patch [1], because
> > both of them changed the _start assembly in arch-riscv.h
>
> That's quite embarrassing, I'm having to trace of that series here. Now
> I can find it in my LKML archives, but I don't have the direct message and
> didn't spot the other ones. I'll have to investigate, thanks for notifying
> me! I'm CCing Thomas, I will check with him how to best merge the two.
I think the conflict should be trivial to fix.
I can also resend my series or just the single riscv patch.
<snip>
Thomas
Powered by blists - more mailing lists