public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "MCC CS" <mcccs@gmx.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: Fold more boolean expressions
Date: Sun, 16 Sep 2018 17:20:00 -0000	[thread overview]
Message-ID: <trinity-aba0276e-5cd4-40c9-9871-b1996ae043e2-1537117103203@3c-app-mailcom-bs15> (raw)
In-Reply-To: <alpine.DEB.2.21.1809141810180.5699@stedding.saclay.inria.fr>

Hi, I have bootstrapped and make check'd my final patch
on latest trunk. Is it OK? Could you please push it
if possible?

The patch can be found here, but please update the commit
message date:
https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00803.html

Test result:

Native configuration is x86_64-pc-linux-gnu

		=== gcc tests ===


Running target unix

		=== gcc Summary ===

# of expected passes		134514
# of expected failures		462
# of unsupported tests		2109
/home/usr/Desktop/gcc-build/gcc/xgcc  version 9.0.0 20180916 (experimental) (GCC) 

		=== g++ tests ===


Running target unix
FAIL: g++.dg/pr80481.C  -std=gnu++98  scan-assembler-not vmovaps
FAIL: g++.dg/pr80481.C  -std=gnu++11  scan-assembler-not vmovaps
FAIL: g++.dg/pr80481.C  -std=gnu++14  scan-assembler-not vmovaps
FAIL: g++.dg/pr83239.C  -std=gnu++98 (test for excess errors)

		=== g++ Summary ===

# of expected passes		127011
# of unexpected failures	4
# of expected failures		532
# of unsupported tests		5028
/home/usr/Desktop/gcc-build/gcc/xg++  version 9.0.0 20180916 (experimental) (GCC) 

		=== libatomic tests ===


Running target unix

		=== libatomic Summary ===

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


Running target unix

		=== libgomp Summary ===

# of expected passes		2031
# of expected failures		1
# of unsupported tests		188
		=== 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		12667
# of expected failures		77
# of unsupported tests		589

Compiler version: 9.0.020180916(experimental)(GCC) 
Platform: x86_64-pc-linux-gnu
configure flags: --enable-languages=c,c++ --prefix=/home/usr/Desktop/gcc-out --with-system-zlib --enable-checking=release --disable-multilib --with-abi=m64

  parent reply	other threads:[~2018-09-16 16:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 13:54 MCC CS
2018-09-11 21:24 ` Marc Glisse
2018-09-14 15:37   ` MCC CS
2018-09-14 16:55     ` Marc Glisse
2018-09-15  8:14       ` MCC CS
2018-09-20 13:34         ` Richard Biener
2018-09-20 14:04           ` Marc Glisse
2018-09-20 14:19             ` Richard Biener
2018-09-22  9:08           ` MCC CS
2018-09-16 17:20       ` MCC CS [this message]
2018-09-30 17:16 MCC CS
2018-10-01  8:39 ` Richard Biener
2018-10-02 14:01   ` MCC CS
2018-10-04  8:08     ` Richard Biener
2018-10-03  8:56 graham stott via gcc-patches

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=trinity-aba0276e-5cd4-40c9-9871-b1996ae043e2-1537117103203@3c-app-mailcom-bs15 \
    --to=mcccs@gmx.com \
    --cc=gcc-patches@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).