Re: gcj segfaults on i686/x86_64-apple-darwin*

[Jack Howarth <howarth at bromo dot med dot uc dot edu>]

On Mon, Nov 09, 2009 at 02:33:11PM +0000, Andrew Haley wrote:
> Jack Howarth wrote:
>
>>    Shouldn't the libjava testsuite contain some rudimentary tests using gcj
>> to make sure it is functional?
>
> Sure.
>
>> The recent testsuite results don't suggest
>> major problems with java on intel darwin...
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2009-11/msg00666.html
>> http://gcc.gnu.org/ml/gcc-testresults/2009-10/msg01308.html
>
> This means that, whatever the cause of the bug, it wasn't present
> when these tests were run.
>
> You can easily verify that yourself by running 'make check-target-libjava'.
>
> Andrew.

Andrew,
   What exactly would I need to add to...

public class testme {
  public static void main(String args[]){
    System.out.println("Hello");
  }
}

to convert it into a libjava compilation/execution test case for gcj?
It might be simplier to just try to run such a test case from within
the libjava dejagnu harness to verify that the issue doesn't exist
within it. I was considering something like...

gcj --main=testme -O pr41991.java

for the compilation and a scan for Hello on the output of the
execution run. Thanks in advance for any hints on where to place
such a test within the libjava dejagnu tests and what header
entries to add.
                Jack