This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.27: 3 weeks till release
- From: Joseph Myers <joseph at codesourcery dot com>
- To: "Dmitry V. Levin" <ldv at altlinux dot org>
- Cc: <libc-alpha at sourceware dot org>
- Date: Thu, 11 Jan 2018 13:45:39 +0000
- Subject: Re: glibc 2.27: 3 weeks till release
- Authentication-results: sourceware.org; auth=none
- References: <20180111034441.GB6991@altlinux.org>
On Thu, 11 Jan 2018, Dmitry V. Levin wrote:
> + RISC-V port
>
> The shared part has been committed, all the rest doesn't affect other
> architectures.
To be precise:
* There are additions to architecture lists in documentation
<https://sourceware.org/ml/libc-alpha/2017-12/msg00915.html>, which affect
shared files, don't seem appropriate to apply without the port itself, but
should be sufficiently safe.
* There are config.h.in additions
<https://sourceware.org/ml/libc-alpha/2017-12/msg00916.html> that also
don't seem appropriate without the port itself but should be safe.
* There are additions of RISC-V configurations to build-many-glibcs.py
<https://sourceware.org/ml/libc-alpha/2017-12/msg00922.html> but that's
inherently safe as build-many-glibcs.py is not part of the normal build /
install process at all.
* There may be documentation for __riscv_flush_icache, requested but not
yet posted <https://sourceware.org/ml/libc-alpha/2018-01/msg00093.html>.
* There may be ldconfig.h and cache.c flag additions for ldconfig support
for multiple RISC-V ABIs, requested but not yet posted
<https://sourceware.org/ml/libc-alpha/2018-01/msg00008.html>.
--
Joseph S. Myers
joseph@codesourcery.com