public inbox for gcc-testresults@sourceware.org
help / color / mirror / Atom feed
From: Andreas Tobler <andreast.dev@gmail.com>
To: <gcc-testresults@gcc.gnu.org>
Subject: Results for 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) testsuite on x86_64-pc-linux-gnu
Date: Tue, 19 Feb 2019 05:35:00 -0000	[thread overview]
Message-ID: <5c6b95b5.1c69fb81.2fa81.1965@mx.google.com> (raw)

LAST_UPDATED: Mon Feb 18 21:38:21 UTC 2019 (revision 268997)

Native configuration is x86_64-pc-linux-gnu

		=== gcc tests ===


Running target unix
FAIL: gcc.target/i386/ifcvt-onecmpl-abs-1.c scan-assembler cltd
FAIL: gcc.target/i386/pr49095.c scan-assembler-times \\\\), % 45
FAIL: gcc.target/i386/pr57193.c scan-assembler-times movdqa 2

		=== gcc Summary ===

# of expected passes		138257
# of unexpected failures	3
# of expected failures		500
# of unsupported tests		2142
/export/devel/build/gcc/head/objdir/gcc/xgcc  version 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) 

		=== gfortran tests ===


Running target unix

		=== gfortran Summary ===

# of expected passes		49013
# of expected failures		121
# of unsupported tests		74
/export/devel/build/gcc/head/objdir/gcc/gfortran  version 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) 

		=== g++ tests ===


Running target unix

		=== g++ Summary ===

# of expected passes		133293
# of expected failures		549
# of unsupported tests		5682
/export/devel/build/gcc/head/objdir/gcc/xg++  version 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) 

		=== objc tests ===


Running target unix

		=== objc Summary ===

# of expected passes		2797
# of expected failures		6
# of unsupported tests		68
/export/devel/build/gcc/head/objdir/gcc/xgcc  version 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) 

		=== libatomic tests ===


Running target unix

		=== libatomic Summary ===

# of expected passes		54
		=== libgomp tests ===


Running target unix

		=== libgomp Summary ===

# of expected passes		6454
# of expected failures		2
# of unsupported tests		349
		=== libitm tests ===


Running target unix

		=== libitm Summary ===

# of expected passes		42
# of expected failures		3
# of unsupported tests		1
		=== libstdc++ tests ===


Running target unix
FAIL: libstdc++-prettyprinters/80276.cc whatis p4
FAIL: libstdc++-prettyprinters/80276.cc whatis p4

		=== libstdc++ Summary ===

# of expected passes		12879
# of unexpected failures	2
# of expected failures		77
# of unsupported tests		589

Compiler version: 9.0.1 20190218 (experimental) [trunk revision 268997] (GCC) 
Platform: x86_64-pc-linux-gnu
configure flags: --prefix=/export/devel/build/gcc/head/testbin


             reply	other threads:[~2019-02-19  5:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  5:35 Andreas Tobler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-19  3:18 H.J. Lu (x32)

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=5c6b95b5.1c69fb81.2fa81.1965@mx.google.com \
    --to=andreast.dev@gmail.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: link
Be 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).