lkml.org 
[lkml]   [2018]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: RFC: remove the "tile" architecture from glibc
On Fri, 9 Mar 2018, John Paul Adrian Glaubitz wrote:

> 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.

"make check", or "make -k check" if you're concerned about some tests
failing to build (e.g. the compiler running out of memory on a few large
tests) - the testsuite should continue after execution failures, but not
after compilation failures. (Having previously configured with
--prefix=/usr for the build. And if the compiler used doesn't have
libgcc_s and libstdc++ shared libraries in directories ld.so searches by
default, you should copy those libraries into the glibc build directory
before running tests.) On a system that can handle it you'd use an
appropriate -jN option for parallelism, but probably not on m68k.

For cross testing over SSH (when glibc is running on a system that is very
slow running the compiler or has too little memory to do so) you need a
shared filesystem at the same path on both the system where glibc is built
and the system where tests will execute (probably NFS-exported from the
build system, and it may be necessary to mount it on the test system with
acdirmax=0,acdirmin=0 to limit any caching). Then you can pass
test-wrapper="/path/to/glibc/scripts/cross-test-ssh.sh <host>" to make
check.

In both cases, for very slow test systems you may wish to export
TIMEOUTFACTOR (an integer by which all test timeouts are multiplied).

--
Joseph S. Myers
joseph@codesourcery.com

\
 
 \ /
  Last update: 2018-03-09 17:54    [W:2.251 / U:0.004 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site