This is the mail archive of the
mailing list for the glibc project.
Re: RISC-V glibc Port v1
- From: Palmer Dabbelt <palmer at dabbelt dot com>
- To: Arnd Bergmann <arnd at arndb dot de>
- Cc: fweimer at redhat dot com
- Cc: libc-alpha at sourceware dot org
- Cc: Andrew Waterman <andrew at sifive dot com>
- Cc: patches at groups dot riscv dot org
- Cc: Darius Rad <darius at bluespec dot com>
- Date: Wed, 14 Jun 2017 14:55:36 -0700 (PDT)
- Subject: Re: RISC-V glibc Port v1
- Authentication-results: sourceware.org; auth=none
On Wed, 14 Jun 2017 14:13:45 PDT (-0700), Arnd Bergmann wrote:
> On Wed, Jun 14, 2017 at 10:35 PM, Florian Weimer <email@example.com> wrote:
>> On 06/14/2017 10:15 PM, Palmer Dabbelt wrote:
>>> Do you have an idea of when there will be a 64-bit time_t clean release? I'd
>>> be OK holding off on the 32-bit port for a bit, as we don't expect RV32I-based
>>> Linux-compatible systems to be popular.
>> Sorry, no idea. I'm Cc:ing Arnd, who believe worked on the kernel side
>> of things.
> Progress has been slow for a while, but there are still a number of interested
> parties, so it is continuing. I don't think it's important to wait
> here, as 64-bit
> time_t will be available for all architectures in glibc once the kernel support
> is done, the question is more about rebuilding all 32-bit binaries in a distro
> after the change.
OK, then I vote we don't wait for RV32 support. While I don't think there's
going to be a flood of RV32 Linux-compatible hardware it'd be easier to port
userspace to both RV32 and RV64 at the same time, rather than doing it twice.
Does that sound OK?