public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Michael Eager <eager@eagerm.com>, Jeff Law <law@redhat.com>,
	 davem@redhat.com, gcc-patches List <gcc-patches@gcc.gnu.org>,
	 java-patches@gcc.gnu.org
Subject: Re: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'
Date: Sun, 05 Oct 2014 03:10:00 -0000	[thread overview]
Message-ID: <5430B7E8.1060001@gmail.com> (raw)
In-Reply-To: <bekwguasixaphab5pghrhbxp.1411603920412@email.android.com>

On 9/25/14 8:12, Chen Gang wrote:
> OK, thanks, next month, I shall try Qemu for microblaze (I also focus on Qemu, and try to make patches for it).
> 
> And, I also need finish the testsuite under Darwin x86_64, next month for gcc.

I finish tried testsuit under Darwin x86_64, originally, I incorrectly
installed mpc: need "brew install libmpc", not "brew install mpc", and
also need "brew link libmpc" which I missed.

At present, except for libjave Throw_2.exe test, I guess all others are
OK, please help check the result below, thanks. 

If it passes checking, next, I shall try to fix libjava Throw_2 issue
within this month (others, include Throw_1 and Throw_3 are all OK).

		=== g++ Summary ===

# of expected passes		82961
# of unexpected failures	891
# of expected failures		255
# of unresolved testcases	272
# of unsupported tests		3421

		=== gcc Summary ===

# of expected passes		85011
# of unexpected failures	30
# of expected failures		182
# of unresolved testcases	10
# of unsupported tests		2796

		=== gfortran Summary ===

# of expected passes		46354
# of unexpected failures	1
# of expected failures		38
# of unsupported tests		74

		=== gnat Summary ===

# of expected passes		799
# of unexpected failures	67
# of unexpected successes	18
# of unresolved testcases	382
# of unsupported tests		8

		=== objc Summary ===

# of expected passes		5828
# of unexpected failures	4
# of expected failures		6
# of unsupported tests		77

		=== boehm-gc Summary ===

# of expected passes		12
# of unsupported tests		1

		=== libatomic Summary ===

# of expected passes		54

		=== libffi Summary ===

# of expected passes		1819
# of unsupported tests		55

		=== libgomp Summary ===

# of expected passes		3194
# of unsupported tests		38

		=== libitm Summary ===

# of expected passes		26
# of expected failures		3
# of unsupported tests		1

		=== libjava Summary ===

# of expected passes		2574
# of unexpected failures	4	/* The 4 issues are all related with Throw_2.exe */
# of expected failures		4
# of untested testcases		4

		=== libstdc++ Summary ===

# of expected passes		8956
# of unexpected failures	159
# of expected failures		69
# of unresolved testcases	38
# of unsupported tests		670


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

       reply	other threads:[~2014-10-05  3:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bekwguasixaphab5pghrhbxp.1411603920412@email.android.com>
2014-10-05  3:10 ` Chen Gang [this message]
2014-10-05  3:26   ` Chen Gang
2014-10-06  4:03     ` Chen Gang
2014-10-06  8:37       ` Libjava test failure Was: " Andrew Haley
2014-10-06 13:48         ` Chen Gang
2014-10-06 13:54           ` Andrew Haley
2014-10-06 14:21             ` Chen Gang
2014-10-06 14:30               ` Andrew Haley
2014-10-06 14:54                 ` Chen Gang
2014-10-06 15:00                   ` Andrew Haley
2014-10-06 15:30                     ` Chen Gang
2014-10-06 17:29                       ` Mike Stump
2014-10-06 23:12                         ` Chen Gang
2014-10-06 23:41                           ` Chen Gang

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=5430B7E8.1060001@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=davem@redhat.com \
    --cc=eager@eagerm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=mikestump@comcast.net \
    /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).