This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RISC-V glibc port, v5
- From: "Richard W.M. Jones" <rjones at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Palmer Dabbelt <palmer at dabbelt dot com>, libc-alpha at sourceware dot org, Andrew Waterman <andrew at sifive dot com>, Darius Rad <darius at bluespec dot com>, dj at redhat dot com, patches at groups dot riscv dot org
- Date: Thu, 25 Jan 2018 19:59:33 +0000
- Subject: Re: RISC-V glibc port, v5
- Authentication-results: sourceware.org; auth=none
- References: <20180125043621.19972-1-palmer@dabbelt.com> <alpine.DEB.2.20.1801251743310.22734@digraph.polyomino.org.uk>
On Thu, Jan 25, 2018 at 05:58:15PM +0000, Joseph Myers wrote:
> On Wed, 24 Jan 2018, Palmer Dabbelt wrote:
>
> > I believe we've taken into account all the feedback, and are now below 20 test
>
> Still missing an ldd_rewrite_script setting as mentioned as needed for
> multi-ABI support in
> <https://sourceware.org/ml/libc-alpha/2018-01/msg00008.html> and
> <https://sourceware.org/ml/libc-alpha/2018-01/msg00521.html>.
>
> The most important thing to figure out at this point - and then stick to
> (changing your mind after the start of the freeze is not a good way to get
> a port into 2.27) - is the choice of exactly what architecture and ABI
> combinations are supported by the port, as that determines what changes
> are needed to have an internally consistent port without lots of
> untestable code for unsupported combinations, and a significant proportion
> of issues from the patch reviews of multiple versions of the RISC-V port
> have been inconsistencies regarding what is supposed to be supported
> (especially when the choice has changed between versions of the port,
> without the changes being carried out consistently through the whole patch
> series).
I don't speak for Palmer nor SiFive, but from my point of view the
urgency to get this in glibc 2.27 is so we can get a stable ABI, which
we can then use to sanely port Fedora & Debian over to RISC-V.
The specific hardware we are targetting initially is the 64 bit SiFive
Freedom U500 [I don't know what the chip will be called in the end -- E500?]
which is RV64GC.
I believe therefore the only stable ABI we care about is rv64gc/lp64d.
Anything else can be unstable/omitted/whatever.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top