This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: remove the "tile" architecture from glibc
- From: Joseph Myers <joseph at codesourcery dot com>
- To: John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin dot de>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 31 Jan 2018 17:37:00 +0000
- Subject: Re: RFC: remove the "tile" architecture from glibc
- Authentication-results: sourceware.org; auth=none
- References: <1a57be83-3349-5450-ee4f-d2a33569a728@mellanox.com> <d6c8e425-a6b6-6594-05e3-965536f06da3@physik.fu-berlin.de> <alpine.DEB.2.20.1712012159490.15078@digraph.polyomino.org.uk> <995aac59-2f9d-2a6a-2b5c-b827410ad295@physik.fu-berlin.de>
On Fri, 1 Dec 2017, John Paul Adrian Glaubitz wrote:
> >> it. I'm pretty sure that there are more than just Mellanox' customers
> >> who are using Linux on Tile.
> >
> > In practice, we need people with architecture expertise to resolve
> > questions that arise about an architecture and review
> > architecture-specific patches, and to run the tests before every release
> > during the release freeze period and fix issues found so the release is in
> > good shape for that architecture.
>
> Yes, I'm aware of that and we in Debian are trying to help in these cases
> where ever we can. We have several porterboxes for powerpc*, sparc*, alpha,
> hppa and more available for porters and we're happy to create accounts for
> anyone from glibc upstream to test any changes. In fact, Adhemerval Zanella
> is already one of these users.
The 2.27 release is due out tomorrow. So far, no test results for tile
have been posted at <https://sourceware.org/glibc/wiki/Release/2.27> - and
the same applies to sh and ia64, which also had some interest in them
expressed in this thread. Are you, or other people you're working with
who have interest in those architectures, working on having results for
those architectures for 2.27 for the wiki page (regenerating libm test
ulps first and getting that regeneration checked in if there would
otherwise be tests failing only because of lack of updated ulps)?
--
Joseph S. Myers
joseph@codesourcery.com