This is the mail archive of the
mailing list for the glibc project.
Re: RISC-V glibc Port v1
- From: Florian Weimer <fweimer at redhat dot com>
- To: Palmer Dabbelt <palmer at dabbelt dot com>
- Cc: libc-alpha at sourceware dot org, Andrew Waterman <andrew at sifive dot com>, patches at groups dot riscv dot org, Darius Rad <darius at bluespec dot com>, Arnd Bergmann <arnd at arndb dot de>
- Date: Wed, 14 Jun 2017 22:35:49 +0200
- Subject: Re: RISC-V glibc Port v1
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=fweimer at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 1C6E220B1E
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1C6E220B1E
- References: <mhng-0841ade8-3952-4e47-8c27-55c8cd09c819@palmer-si-x1c4>
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
> One sticking point is that the RV32I and RV64I base ISAs are very similar, and
> as such share a lot of code. I'd prefer to avoid removing the rv32 code just
> to add it back in later, as that will be a big headache.
> Would it be sufficient to just disallow RV32I in our preconfigure with a patch
> like this, and then turn RV32I back on when we can support a 64-bit time_t
> clean ABI?
I think that would be acceptable. aarch64 is basically in the same boat
today (but they want to use a 32-bit time_t for their ILP32 port).