tests failing on x86_64-linux

[H.J. Lu]

On Wed, Dec 9, 2020 at 2:31 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Wed, Dec 9, 2020 at 1:44 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Wed, Dec 9, 2020 at 1:17 PM Martin Sebor <msebor@gmail.com> wrote:
> > >
> > > On 12/9/20 11:28 AM, H.J. Lu wrote:
> > > > On Wed, Dec 9, 2020 at 10:17 AM Martin Sebor via Libc-alpha
> > > > <libc-alpha@sourceware.org> wrote:
> > > >>
> > > >> I've been seeing quite a few test failures in recent builds, more
> > > >> than I used to in the past.  Are those expected?  I configure with
> > > >> no options other than --prefix=/usr and after building without
> > > >> installing (i.e., just make -j16) run make -j16 check.
> > > >>
> > > >> The results below are for the top of GCC/Glibc trunk on x86_64
> > > >> Fedora Linux but I don't think using GCC 10 improves things much
> > > >> if at all.
> > > >>
> > > >
> > > > "make check" is clean for me on Fedora 33/x86-64.  Please make sure that
> > > > you have all required packages installed, including libstdc++-static.
> > > >
> > >
> > > It's been a while since I built Glibc with the system compiler
> > > so I must have misremembered the results.  Here they are for
> > > my Fedora 29 machine (with libstdc++-static installed and with
> > > --prefix=/usr):
> > >
> > > gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC)
> > >
> > > UNSUPPORTED: assert/tst-assert-c++
> > > UNSUPPORTED: assert/tst-assert-g++
> > > UNSUPPORTED: debug/tst-chk4
> > > UNSUPPORTED: debug/tst-chk5
> > > UNSUPPORTED: debug/tst-chk6
> > > UNSUPPORTED: debug/tst-lfschk4
> > > UNSUPPORTED: debug/tst-lfschk5
> > > UNSUPPORTED: debug/tst-lfschk6
> > > UNSUPPORTED: dlfcn/bug-atexit3
> > > UNSUPPORTED: elf/tst-audit10
> > > UNSUPPORTED: elf/tst-avx512
> > > UNSUPPORTED: elf/tst-env-setuid
> > > UNSUPPORTED: elf/tst-env-setuid-tunables
> > > XPASS: elf/tst-protected1a
> > > XPASS: elf/tst-protected1b
> > > UNSUPPORTED: math/test-double-libmvec-sincos-avx512
> > > UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
> > > UNSUPPORTED: misc/tst-pkey
> > > UNSUPPORTED: nptl/tst-cancel24
> > > UNSUPPORTED: nptl/tst-cancel24-static
> > > UNSUPPORTED: nptl/tst-minstack-throw
> > > UNSUPPORTED: nptl/tst-once5
> > > UNSUPPORTED: nptl/tst-thread-exit-clobber
> > > UNSUPPORTED: nptl/tst-thread_local1
> > > UNSUPPORTED: stdlib/tst-quick_exit
> > > UNSUPPORTED: stdlib/tst-thread-quick_exit
> > > Summary of test results:
> > >     4214 PASS
> > >       24 UNSUPPORTED
> > >       16 XFAIL
> > >        2 XPASS
> > >
> > > And below are the results I see with today's top of GCC trunk.
> > > All the failures are due to "original exit status 127" which IIUC
> > > means the program wasn't found.  Yet they're all there.  Could it
> > > have something to do with the paralellization?  The other
> > > difference between the native build and my GCC 11 build is that
> > > the latter is an unoptimized GCC so it takes quite a bit longer
> > > to compile.
> > >
> > > gcc version 11.0.0 20201209 (experimental) (GCC)
> >
> > Did you apply
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561332.html
>
> Using built-in specs.
> COLLECT_GCC=/usr/gcc-11.0.0-x32/bin/gcc
> COLLECT_LTO_WRAPPER=/usr/gcc-11.0.0-x32/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper
> Target: x86_64-pc-linux-gnu
> Configured with: /export/gnu/import/git/gitlab/x86-gcc/configure
> --enable-cet --with-demangler-in-ld --prefix=/usr/gcc-11.0.0-x32
> --with-local-prefix=/usr/local --enable-gnu-indirect-function
> --enable-clocale=gnu --with-system-zlib --with-target-system-zlib
> --with-fpmath=sse --with-multilib-list=m32,m64,mx32
> --enable-linker-build-id --enable-gnu-unique-object
> --enable-languages=c,c++,fortran,lto,objc,obj-c++,go
> Thread model: posix
> Supported LTO compression algorithms: zlib zstd
> gcc version 11.0.0 20201204 (experimental) (GCC)
>
> is "makc check" clean.  I will test r11-5888 + my PR target/98146 patches.

r11-5888 is also "make check" clean.

-- 
H.J.