Re: Libjava test failure Was: [PATCH] microblaze: microblaze.md: Use 'SI' instead of 'VOID' for operand 1 of 'call_value_intern'

[Mike Stump <mikestump@comcast.net>]

On Oct 6, 2014, at 8:36 AM, Chen Gang <gang.chen.5i5j@gmail.com> wrote:
> For me, "make -k check" is suitable for one sub-system (e.g. for cross
> building, and mainly focus on gcc), but not for global check (full
> non-cross building check):

In our world, there is no sub-system, so, talk of such is outside the scope of gcc.

Let me repeat what he said differently.

You have two choices, fixing the port so that there are no unexpected failures or running check with -k.

I’d like to get to the point where all primary/secondary platforms can use make check directly, we’re not there yet.

The idea is that the single return value tells if if the suite passed or not.  This is an absolute measure, that, when achieved means one never has to compare previous/present results, just know that the suite passed.  Sometimes simple is better.

> - "make check" is the standard check for global,

No sub-system, no global.