From: Charlie Jenkins <charlie@rivosinc.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: linux-next: Tree for Nov 15 (RV32: arch/riscv/kernel/tests/module_test/test_uleb128.S)
Date: Fri, 17 Nov 2023 12:12:45 -0500 [thread overview]
Message-ID: <ZVefDTKIeGa+ts3f@ghost> (raw)
In-Reply-To: <1d7c71ee-5742-4df4-b8ef-a2aea0a624eb@infradead.org>
On Wed, Nov 15, 2023 at 01:01:24PM -0800, Randy Dunlap wrote:
>
>
> On 11/14/23 17:27, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20231114:
> >
>
> (using gcc 13.2.0 from kernel.org)
>
> on riscv 32-bit:
>
> arch/riscv/kernel/tests/module_test/test_uleb128.S: Assembler messages:
> arch/riscv/kernel/tests/module_test/test_uleb128.S:9: Error: unrecognized opcode `ld a0,second'
> arch/riscv/kernel/tests/module_test/test_uleb128.S:15: Error: unrecognized opcode `ld a0,fourth'
> riscv32-linux-ld: cannot find arch/riscv/kernel/tests/module_test/test_uleb128.o: No such file or directory
>
>
> Full randconfig file is attached.
>
> Is this a toolchain problem?
>
> thanks.
> --
> ~Randy
I had an assumption when writing this code that uleb128 was only
supported on rv64 toolchains. Since it appears that there do exist rv32
toolchains with uleb128 support I will modify this test to be supported
on rv32 platforms.
The config AS_HAS_ULEB128 in arch/riscv/kernel/tests/Kconfig.debug
should be auto-set to N if the toolchain does not support ULEB128 even though
the randconfig has CONFIG_AS_HAS_ULEB128=y.
There are a couple of sparse warnings in this series that I will fix up
and send out in a new series with this fix.
- Charlie
prev parent reply other threads:[~2023-11-17 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 1:27 linux-next: Tree for Nov 15 Stephen Rothwell
2023-11-15 21:01 ` linux-next: Tree for Nov 15 (RV32: arch/riscv/kernel/tests/module_test/test_uleb128.S) Randy Dunlap
2023-11-17 17:12 ` Charlie Jenkins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVefDTKIeGa+ts3f@ghost \
--to=charlie@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox