From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Joseph Myers <joseph@codesourcery.com>
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, 9 Mar 2018 17:37:15 +0100 [thread overview]
Message-ID: <224c8996-bda1-5e75-bff3-9ed8abc4de87@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1803091622420.8457@digraph.polyomino.org.uk>
On 03/09/2018 05:31 PM, Joseph Myers wrote:
> 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.)
Ok, thanks for the explanation.
On a sidenote: Is there documentation somewhere which explains how to properly
run the glibc testsuite? I would then go ahead and run it on my Amiga 4000
for m68k.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2018-03-09 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a57be83-3349-5450-ee4f-d2a33569a728@mellanox.com>
[not found] ` <d6c8e425-a6b6-6594-05e3-965536f06da3@physik.fu-berlin.de>
[not found] ` <abce89d0-6798-069a-1a54-06e664665b78@mellanox.com>
[not found] ` <dc3c52ce-f082-0da0-7828-0d4e6751e2a5@physik.fu-berlin.de>
2018-03-07 15:39 ` Arnd Bergmann
2018-03-07 16:00 ` Joseph Myers
2018-03-07 16:08 ` John Paul Adrian Glaubitz
2018-03-07 18:14 ` 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
2018-03-09 16:37 ` John Paul Adrian Glaubitz [this message]
2018-03-09 16:53 ` Joseph Myers
2018-03-08 17:14 ` Palmer Dabbelt
2018-03-08 23:36 ` Arnd Bergmann
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=224c8996-bda1-5e75-bff3-9ed8abc4de87@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=helmut@subdivi.de \
--cc=hgb@ifi.uio.no \
--cc=joseph@codesourcery.com \
--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
all inboxes | Powered by JetHome®