This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2 00/12] RISC-V glibc port for the 32 bit
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Zong Li <zongbox at gmail dot com>
- Cc: Zong Li <zong at andestech dot com>, Palmer Dabbelt <palmer at dabbelt dot com>, <darius at bluespec dot com>, Andrew Waterman <andrew at sifive dot com>, <dj at redhat dot com>, <rth at twiddle dot net>, <libc-alpha at sourceware dot org>, <rth7680 at gmail dot com>
- Date: Wed, 18 Jul 2018 20:53:59 +0000
- Subject: Re: [PATCH v2 00/12] RISC-V glibc port for the 32 bit
- References: <firstname.lastname@example.org> <alpine.DEB.email@example.com> <CA+ZOyagPKraOf5H17WmYJw4aFJLXk-Yp-Zc2YS=QGRxBxE-6XQ@mail.gmail.com>
On Wed, 18 Jul 2018, Zong Li wrote:
> > * 32-bit RISC-V support was omitted from 2.27 because the Linux kernel
> > support was in too poor shape to be able to run the testsuite. Thus, you
> > need to confirm what upstream Linux kernel version had good-enough support
> > for 32-bit RISC-V, and set arch_minimum_kernel accordingly.
> I had submitted some patches for 32-bit Linux on RISC-V. For now, the
> upstream kernel
> can build successfully and run the glibc testsutie.
What upstream kernel version *has a stable kernel/userspace ABI* for RV32
and *is stable enough to run the glibc testsuite*? I'd expect that to go
<https://sourceware.org/ml/libc-alpha/2018-07/msg00447.html> appear to aim
to remove legacy stat syscall families from new architectures, so
requiring them to implement stat functions in terms of statx in userspace.
The former, in particular, identifies RV32 as an architecture not needing
backwards compatibility for the old syscalls.
Supposing those patches (that whole 17-patch series) are applied to the
Linux kernel, what stat syscalls does it provide for RV32 (and RV64) and
does your glibc port for RV32 properly work with that set of syscalls?
Joseph S. Myers