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

Chen Gang
Mon Oct 6 23:41:00 GMT 2014

On 10/7/14 7:18, Chen Gang wrote:
> On 10/7/14 1:29, Mike Stump wrote:
>> On Oct 6, 2014, at 8:36 AM, Chen Gang <> 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.
> Theoretically, in each system (include gcc), always can be separated
> into several 'sub-systems', and then 'global' means the system itself.
> In our case, we say let 'global' pass checking means let gcc, gfortran,
> g++, libjava ... all pass checking. But for mainly focus on constructing
> environments, I will try to use upstream glibc instead of Darwin glibc:
>  - If fix Throw_2, we know it is environments construction issue.
>  - Else, I shall skip it (since "make -k check" should be OK).
> And after finish testsuite under Darwin, within this month, I shall try
> to find and send a patch for gcc, and pass testsuite under Darwin (it
> seems it is not quite difficult to me).

It is really unlucky, The upstream glibc does not support Darwin! And
sorry, send patches to glibc is really out of my current border, so I
have to give up. :-(

  bash-3.2# ../glibc/configure --with-prefix=/release/Darwin/ --with-sysroot=/release/Darwin
  checking build system type... x86_64-apple-darwin13.4.0
  checking host system type... x86_64-apple-darwin13.4.0
  checking for gcc... gcc
  checking for suffix of object files... o
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for g++... g++
  checking whether we are using the GNU C++ compiler... yes
  checking whether g++ accepts -g... yes
  checking for readelf... no
  checking for sysdeps preconfigure fragments... aarch64 alpha arm hppa i386 m68k microblaze mips powerpc s390 sh sparc tile x86_64 checking whether gcc compiles in -mx32 mode by default... no
  configure: running configure fragment for add-on libidn
  *** The GNU C library is currently not available for this platform.
  *** So far nobody cared to port it and if there is no volunteer it
  *** might never happen.  So, if you have interest to see glibc on
  *** this platform visit
  *** and join the group of porters

And I guess, this thread can be ended, and next, I shall try to find a
patch for gcc, and let it pass testsuite under Darwin.

Chen Gang

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

More information about the Java-patches mailing list