Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: "Billinghurst, David (CRTS)" <David DOT Billinghurst AT riotinto DOT com>
Cc: <java AT gcc DOT gnu DOT org>, <cygwin AT cygwin DOT com>
Subject: Re: java on cygwin - 2082 tests pass
References: <FAC87D7C874EAB46A847604DA4FD5A64034717 AT crtsmail DOT corp DOT riotinto DOT org>
From: Tom Tromey <tromey AT redhat DOT com>
Reply-To: tromey AT redhat DOT com
X-Attribution:  Tom
X-Zippy:  ..  Like I always say -- nothing can beat the BRATWURST
 here in DUSSELDORF!!
Date: 08 May 2002 10:05:30 -0600
In-Reply-To: "Billinghurst, David's message of "Wed, 8 May 2002 23:04:58 +1000"
Message-ID: <87it5ysjzp.fsf@creche.redhat.com>
Lines: 48

>>>>> "David" == Billinghurst, David (CRTS) <David DOT Billinghurst AT riotinto DOT com> writes:

David>  - CYGWIN=check_case:strict
David>  - rebuilt binutils with 16-byte alignment
David>  - (and a small testsuite cheat) 

I assume you are building with threads enabled?
As I understand it the GC currently doesn't support threads on Cygwin,
though Hans has a pending patch.

David> FAIL: Array_3 execution from source compiled test

This tests null pointer exception creation and handling.

David> FAIL: Divide_1 execution from source compiled test

This tests divide by zero exception creation and handling.

David> FAIL: KeepInline output from source compiled test

From the test:

    // Demonstrate that private methods can be reflected even if they are
    // not referenced at compile-time (i.e. -fkeep-inline-functions works).

It is odd that this one fails.  What happens?

David> FAIL: SyncTest execution from bytecode->native test
David> FAIL: Thread_Interrupt output from source compiled test
David> FAIL: Thread_Wait_Interrupt output from bytecode->native test

These all require threads.

David> FAIL: Throw_2 execution from source compiled test

This is another null pointer exception creation and handling test.

Overall this is pretty good.  To me it says:

* You need threads to work
* The signal-to-exception code isn't working.  That's not too
  surprising.  Maybe Cygwin needs to use the
  SetUnhandledExceptionFilter code from win32.cc?
  (I'm assuming it doesn't already.)

KeepInline is the only mystery.

Tom

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/