From: Joseph Myers <joseph@codesourcery.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Arnd Bergmann <arnd@arndb.de>, Helmut Grohne <helmut@subdivi.de>,
GNU C Library <libc-alpha@sourceware.org>,
linux-arch <linux-arch@vger.kernel.org>, <metcalf@alum.mit.edu>,
Henrik Grindal Bakken <hgb@ifi.uio.no>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: remove the "tile" architecture from glibc
Date: Fri, 09 Mar 2018 16:31:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1803091622420.8457@digraph.polyomino.org.uk> (raw)
In-Reply-To: <9a60ac70-21e4-3f48-5cd7-ffd3aabc5c21@physik.fu-berlin.de>
On Thu, 8 Mar 2018, John Paul Adrian Glaubitz wrote:
> I have personally invested a lot of work into the SH port over the
> past three years in Debian and I was involved fixing many bugs
> and as a result, the port is quite usable. It would be really
> disappointing to see it being removed all of a sudden :(.
Note that SH glibc test results need some work - there are a large number
of failures listed at <https://sourceware.org/glibc/wiki/Release/2.27#SH>.
Probably most could be addressed with the NaN fixes I outlined at
<https://sourceware.org/ml/libc-alpha/2018-02/msg00440.html> - but that
does of course need someone to do the work to implement that in GCC and
glibc. (The stdlib/tst-tininess failure is stranger; SH manuals don't
seem very specific on this, but the existing setting was definitely
determined by testing on hardware. SH experts with access to a range of
different hardware may be needed to advise on what different hardware does
or is supposed to do in this regard.)
The glibc port whose test results cause me the most concern that it's
effectively unmaintained and should be considered for obsoletion is
MicroBlaze - the results
<https://sourceware.org/glibc/wiki/Release/2.27#MicroBlaze> are clearly a
big mess (not something where one fix would probably resolve most failures
as on SH) and there's no sign of activity to sort them out (nor has there
been such activity for a long time).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-03-09 16:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 21:34 Chris Metcalf
2017-12-01 21:41 ` Joseph Myers
2017-12-01 21:57 ` John Paul Adrian Glaubitz
2017-12-01 22:11 ` Joseph Myers
2017-12-01 22:30 ` John Paul Adrian Glaubitz
2017-12-01 22:41 ` Joseph Myers
2017-12-02 15:15 ` John Paul Adrian Glaubitz
2017-12-04 11:10 ` Adhemerval Zanella
2017-12-04 11:28 ` John Paul Adrian Glaubitz
2017-12-04 18:03 ` Joseph Myers
2017-12-04 18:32 ` Adhemerval Zanella
2017-12-04 18:55 ` Joseph Myers
2017-12-04 18:14 ` Chris Metcalf
2017-12-04 18:36 ` Adhemerval Zanella
2017-12-04 17:53 ` Joseph Myers
2017-12-04 18:47 ` John Paul Adrian Glaubitz
2017-12-04 19:02 ` Joseph Myers
[not found] ` <alpine.DEB.2.20.1801311732001.23883@digraph.polyomino.org.uk>
[not found] ` <38170271-e17f-0a7e-7dd2-06fa6ddfae62@physik.fu-berlin.de>
[not found] ` <9f8b994a-7085-e263-dd1b-bea2def55fb0@linaro.org>
2018-02-01 13:24 ` Adhemerval Zanella
2018-02-01 13:33 ` John Paul Adrian Glaubitz
2018-02-01 13:37 ` Adhemerval Zanella
2018-02-01 13:45 ` Joseph Myers
2018-02-01 16:40 ` Adhemerval Zanella
2018-02-01 13:39 ` Joseph Myers
2018-02-01 17:21 ` Adhemerval Zanella
2018-02-01 17:52 ` Joseph Myers
2018-02-01 18:30 ` Joseph Myers
2018-02-14 18:13 ` Joseph Myers
2018-02-01 13:34 ` Adhemerval Zanella
2018-02-01 13:50 ` Joseph Myers
2018-02-01 16:50 ` Adhemerval Zanella
2017-12-02 1:15 ` Chris Metcalf
2017-12-02 15:16 ` John Paul Adrian Glaubitz
2017-12-04 21:49 ` Chris Metcalf
2017-12-04 23:29 ` Joseph Myers
2018-03-07 15:39 ` Arnd Bergmann
2018-03-07 16:01 ` Joseph Myers
2018-03-07 16:08 ` John Paul Adrian Glaubitz
2018-03-07 16:49 ` Adhemerval Zanella
2018-03-07 17:17 ` Joseph Myers
2018-03-07 18:16 ` Helmut Grohne
2018-03-08 15:55 ` Arnd Bergmann
2018-03-08 16:06 ` John Paul Adrian Glaubitz
2018-03-08 16:23 ` Arnd Bergmann
2018-03-09 16:31 ` Joseph Myers [this message]
2018-03-09 16:37 ` John Paul Adrian Glaubitz
2018-03-09 16:53 ` Joseph Myers
2018-03-08 17:14 ` Palmer Dabbelt
2018-03-08 23:36 ` Arnd Bergmann
2017-12-02 3:24 ` Carlos O'Donell
2017-12-08 16:20 ` Chris Metcalf
2018-01-05 9:01 ` Henrik Grindal Bakken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1803091622420.8457@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=arnd@arndb.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=helmut@subdivi.de \
--cc=hgb@ifi.uio.no \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metcalf@alum.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).