[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1479419136.908.90.camel@caviumnetworks.com>
Date: Thu, 17 Nov 2016 13:45:36 -0800
From: Steve Ellcey <sellcey@...iumnetworks.com>
To: Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
Yury Norov <ynorov@...iumnetworks.com>
CC: <arnd@...db.de>, <catalin.marinas@....com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-arch@...r.kernel.org>,
GNU C Library <libc-alpha@...rceware.org>,
<schwidefsky@...ibm.com>, <heiko.carstens@...ibm.com>,
Andrew Pinski <pinskia@...il.com>, <broonie@...nel.org>,
"Joseph S. Myers" <joseph@...esourcery.com>,
<christoph.muellner@...obroma-systems.com>,
<bamvor.zhangjian@...wei.com>,
Szabolcs Nagy <szabolcs.nagy@....com>,
<klimov.linux@...il.com>, <Nathan_Lynch@...tor.com>,
<agraf@...e.de>, Prasun Kapoor <Prasun.Kapoor@...iumnetworks.com>,
<kilobyte@...band.pl>, Geert Uytterhoeven <geert@...ux-m68k.org>,
"Dr. Philipp Tomsich" <philipp.tomsich@...obroma-systems.com>,
<manuel.montezelo@...il.com>, <linyongting@...wei.com>,
<davem@...emloft.net>, <zhouchengming1@...wei.com>,
<cmetcalf@...hip.com>,
Adhemerval Zanella <adhemerval.zanella@...aro.org>
Subject: Re: ILP32 for ARM64: testing with glibc testsuite
On Wed, 2016-11-16 at 15:22 +0400, Maxim Kuvyrkov wrote:
> >
> > On Nov 9, 2016, at 1:56 PM, Yury Norov <ynorov@...iumnetworks.com>
> > wrote:
> >
> > >
> > > Below is the results of glibc testsuite run for aarch64/lp64
I have been running the glibc testsuite as well. I have only run it on
an ILP32 enabled kernel. Using that kernel, top-of-tree glibc, and the
ILP32 glibc patches I have no LP64 regressions. There are 5 failures
in LP64 mode but I get them with vanilla top-of-tree glibc sources too.
They are:
nptl/eintr1 (I actually don't run this because it kills the 'make check')
debug/tst-backtrace5
debug/tst-backtrace6
nptl/tst-stack4
nptl/tst-thread_local1
In ILP32 mode I get 33 failures, they include the above failures (minus
nptl/tst-thread_local1) plus:
c++-types-check
conform/ISO11/inttypes.h/conform
conform/ISO11/stdint.h/conform
conform/ISO99/inttypes.h/conform
conform/ISO99/stdint.h/conform
conform/POSIX2008/inttypes.h/conform
conform/POSIX2008/stdint.h/conform
conform/XOPEN2K/inttypes.h/conform
conform/XOPEN2K/stdint.h/conform
conform/XOPEN2K8/inttypes.h/conform
conform/XOPEN2K8/stdint.h/conform
elf/tst-tls1
elf/tst-tls1-static
elf/tst-tls2
elf/tst-tls2-static
elf/tst-tls3
math/check-abi-libm
math/test-double
math/test-double-finite
math/test-float
math/test-float-finite
misc/tst-sync_file_range
nptl/tst-cancel26
nptl/tst-cancel27
nptl/tst-sem3
rt/tst-mqueue1
rt/tst-mqueue2
rt/tst-mqueue4
rt/tst-mqueue7
stdlib/tst-makecontext3
I am currently looking at these ILP32 regressions (starting with the
tls failures) to see if I can figure out what is happening with them.
Steve Ellcey
sellcey@...iumnetworks.com
Powered by blists - more mailing lists