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: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- To: libc-alpha at sourceware dot org
- Date: Thu, 1 Feb 2018 11:34:12 -0200
- 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> <alpine.DEB.2.20.1801311732001.23883@digraph.polyomino.org.uk> <38170271-e17f-0a7e-7dd2-06fa6ddfae62@physik.fu-berlin.de>
On 31/01/2018 16:15, John Paul Adrian Glaubitz wrote:
> On 01/31/2018 06:37 PM, Joseph Myers wrote:
>> 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)?
>
> I don't have access to tile hardware at the moment, but sh4 and ia64.
>
> Adhemerval has access to the sparc64, sh4 and ia64 boxes as well and
> he said he would be working on the ia64 stuff.
>
> If he doesn't run the testsuite on these architectures, I can do that
> later next week.
>
> Adrian
>
Hi Adrian,
Trying to build/run glibc testsuite against sh4 own toolchain I am facing
an build issue for some tests:
---
gcc -nostdlib -nostartfiles -o /home/azanella/glibc/glibc-git-build/assert/tst-assert-c++ -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both /home/azanella/glibc/glibc-git-build/csu/crt1.o /home/azanella/glibc/glibc-git-build/csu/crti.o `gcc --print-file-name=crtbegin.o` /home/azanella/glibc/glibc-git-build/assert/tst-assert-c++.o /home/azanella/glibc/glibc-git-build/support/libsupport_nonshared.a -lstdc++ -Wl,-dynamic-linker=/lib/ld-linux.so.2 -Wl,-rpath-link=/home/azanella/glibc/glibc-git-build:/home/azanella/glibc/glibc-git-build/math:/home/azanella/glibc/glibc-git-build/elf:/home/azanella/glibc/glibc-git-build/dlfcn:/home/azanella/glibc/glibc-git-build/nss:/home/azanella/glibc/glibc-git-build/nis:/home/azanella/glibc/glibc-git-build/rt:/home/azanella/glibc/glibc-git-build/resolv:/home/azanella/glibc/glibc-git-build/crypt:/home/azanella/glibc/glibc-git-build/mathvec:/home/azanella/glibc/glibc-git-build/support:/home/azanella/glibc/glibc-git-build/nptl /home/azanella/glibc/glibc-git-build/libc.so.6 /home/azanella/glibc/glibc-git-build/libc_nonshared.a -Wl,--as-needed /home/azanella/glibc/glibc-git-build/elf/ld.so -Wl,--no-as-needed -lgcc -Wl,--as-needed -lgcc_s -Wl,--no-as-needed `gcc --print-file-name=crtend.o` /home/azanella/glibc/glibc-git-build/csu/crtn.o
/usr/lib/gcc/sh4-linux-gnu/7/libgcc_s.so.1: undefined reference to `__fpscr_values@GLIBC_2.2'
collect2: error: ld returned 1 exit status
---
I did not dig into this, but some google shows it has been an issue before [1].
The issue is using build-many-glibcs.py cross toolchain I did not see any
issues building glibc testsuite.
The major gcc configuration differences I see is system one adds a
'--with-cpu=sh4 --with-multilib-list=m4,m4-nofpu'. Any idea of what might
be happening.
[1] https://sourceware.org/ml/libc-alpha/2009-01/msg00034.html