public inbox for gcc-testresults@sourceware.org help / color / mirror / Atom feed
From: "Bill Seurer (POWER9)" <seurer@linux.ibm.com> To: gcc-testresults@gcc.gnu.org Subject: Results for 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) testsuite on powerpc64le-unknown-linux-gnu Date: Tue, 19 Feb 2019 22:41:00 -0000 [thread overview] Message-ID: <20190219224127.GA141361@marlin.aus.stglabs.ibm.com> (raw) Linux 4.15.0-43-generic ppc64le GNU ld (GNU Binutils for Ubuntu) 2.30 GNU assembler (GNU Binutils for Ubuntu) 2.30 GNU Make 4.1 DejaGnu: DejaGnu version 1.6.1 Expect version 5.45.4 Tcl version 8.6 64-bit LAST_UPDATED: Tue Feb 19 19:35:03 UTC 2019 (revision 269028) Native configuration is powerpc64le-unknown-linux-gnu === g++ tests === Running target unix FAIL: c-c++-common/attr-nonstring-6.c -std=gnu++11 (test for excess errors) FAIL: c-c++-common/attr-nonstring-6.c -std=gnu++14 (test for excess errors) FAIL: c-c++-common/attr-nonstring-6.c -std=gnu++98 (test for excess errors) FAIL: g++.dg/pr83239.C -std=gnu++98 (test for excess errors) === g++ Summary === # of expected passes 124637 # of unexpected failures 4 # of expected failures 510 # of unsupported tests 5423 /home/gccbuild/build/nightly/build-gcc-8/gcc/xg++ version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === gcc tests === Running target unix FAIL: c-c++-common/attr-nonstring-6.c -Wc++-compat (test for excess errors) XPASS: gcc.dg/Wtrampolines.c standard descriptors (test for warnings, line 29) FAIL: gcc.dg/sms-10.c scan-rtl-dump-times sms "SMS succeeded" 1 XPASS: gcc.dg/graphite/pr69728.c scan-tree-dump graphite "loop nest optimized" FAIL: gcc.dg/ipa/iinline-attr.c scan-ipa-dump inline "hooray[^\\\\n]*inline copy in test" FAIL: gcc.dg/torture/float128-cmp-invalid.c -O0 execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -O1 execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -O3 -g execution test FAIL: gcc.dg/torture/float128-cmp-invalid.c -Os execution test FAIL: gcc.dg/torture/pr52451.c -O0 execution test FAIL: gcc.dg/torture/pr52451.c -O1 execution test FAIL: gcc.dg/torture/pr52451.c -O2 execution test FAIL: gcc.dg/torture/pr52451.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: gcc.dg/torture/pr52451.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: gcc.dg/torture/pr52451.c -O3 -g execution test FAIL: gcc.dg/torture/pr52451.c -Os execution test XPASS: gcc.dg/tree-ssa/ssa-dom-cse-2.c scan-tree-dump optimized "return 28;" XPASS: gcc.dg/vect/vect-24.c -flto -ffat-lto-objects scan-tree-dump-times vect "vectorized 3 loops" 1 XPASS: gcc.dg/vect/vect-24.c scan-tree-dump-times vect "vectorized 3 loops" 1 XPASS: gcc.target/powerpc/20050603-3.c scan-assembler-not \\\\mrlwinm XPASS: gcc.target/powerpc/20050603-3.c scan-assembler-times \\\\mrl[wd]imi 1 FAIL: gcc.target/powerpc/altivec-7-le.c scan-assembler-times vupkhpx 1 FAIL: gcc.target/powerpc/vsx-7-be.c scan-assembler-times vupkhpx 1 === gcc Summary === # of expected passes 119802 # of unexpected failures 19 # of unexpected successes 7 # of expected failures 431 # of unsupported tests 2390 /home/gccbuild/build/nightly/build-gcc-8/gcc/xgcc version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === gfortran tests === Running target unix FAIL: gfortran.dg/elemental_subroutine_3.f90 -O1 (test for excess errors) FAIL: gfortran.dg/elemental_subroutine_3.f90 -O2 (test for excess errors) FAIL: gfortran.dg/elemental_subroutine_3.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gfortran.dg/elemental_subroutine_3.f90 -O3 -g (test for excess errors) FAIL: gfortran.dg/elemental_subroutine_3.f90 -Os (test for excess errors) XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O2 execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O3 -g execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -Os execution test FAIL: gfortran.dg/ieee/large_2.f90 -O0 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O1 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O2 execution test FAIL: gfortran.dg/ieee/large_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: gfortran.dg/ieee/large_2.f90 -O3 -g execution test FAIL: gfortran.dg/ieee/large_2.f90 -Os execution test === gfortran Summary === # of expected passes 47817 # of unexpected failures 11 # of unexpected successes 6 # of expected failures 105 # of unsupported tests 105 /home/gccbuild/build/nightly/build-gcc-8/gcc/gfortran version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === go tests === Running target unix FAIL: go.test/test/ken/cplx2.go execution, -O2 -g === go Summary === # of expected passes 7281 # of unexpected failures 1 # of expected failures 1 # of untested testcases 7 # of unsupported tests 3 /home/gccbuild/build/nightly/build-gcc-8/gcc/gccgo version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === obj-c++ tests === Running target unix === obj-c++ Summary === # of expected passes 1456 # of expected failures 10 # of unsupported tests 77 /home/gccbuild/build/nightly/build-gcc-8/gcc/xg++ version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === objc tests === Running target unix === objc Summary === # of expected passes 2803 # of unsupported tests 68 /home/gccbuild/build/nightly/build-gcc-8/gcc/xgcc version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === gotools tests === === gotools Summary === # of expected passes 383 # of untested testcases 195 /home/gccbuild/build/nightly/build-gcc-8/./gcc/gccgo version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === libatomic tests === Running target unix === libatomic Summary === # of expected passes 54 === libffi tests === Running target unix === libffi Summary === # of expected passes 1934 # of unsupported tests 28 === libgo tests === Running target unix FAIL: runtime FAIL: os/signal === libgo Summary === # of expected passes 161 # of unexpected failures 2 /home/gccbuild/build/nightly/build-gcc-8/./gcc/gccgo version 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) === libgomp tests === Running target unix === libgomp Summary === # of expected passes 5455 # of expected failures 2 # of unsupported tests 363 === libitm tests === Running target unix === libitm Summary === # of expected passes 42 # of expected failures 3 # of unsupported tests 1 === libstdc++ tests === Running target unix === libstdc++ Summary === # of expected passes 12441 # of expected failures 71 # of unsupported tests 573 Compiler version: 8.2.1 20190219 [gcc-8-branch revision 269028] (GCC) Platform: powerpc64le-unknown-linux-gnu configure flags: --prefix=/opt/gcc-nightly/8 --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++,fortran,objc,obj-c++,go --with-cpu=power9
reply other threads:[~2019-02-19 22:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190219224127.GA141361@marlin.aus.stglabs.ibm.com \ --to=seurer@linux.ibm.com \ --cc=gcc-testresults@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).