java-interop: reachability test for catch statement does not understand java checked exceptions
Stop converting unknown Java exception to x10
java-interop: reachability analysis is broken with Java exception
In r23358, stopped converting j.l.
They no longer have x10 type name but they should be able to catch with Java type name.
In r23359, restored conversion from j.l.
to fix regression with test_matrix_runtime_error1 and FutureTest3.
There seems to be bad interaction between -NO_CHECKS and Java exception conversion logic which bypasses conversion of Java exceptions such as j.l.AssertionError or j.l.ArrayIndexOutOfBoundsException.
In r23386, committed the second trial for stopping conversion from j.l.
In r23420, changed the order of catch blocks so that handlers for x10 throwables can work correctly.
In r23422, implemented rethrow mechanism for x10 throwables that are caught by handlers for java throwables.
Fixed in r23422
In r23439, simplified rethrow mechanism using single rethrow block (follow-on).
Committed bug fixes in r23466 and r23469. Still work in progress.
Fixed bugs related with unwrapping UnknownJavaThrowable and catching constrained type in r23471.
bulk close of 2.2.2 resolved issues.