[ http://issues.apache.org/jira/browse/HARMONY-1802?page=comments#action_12441423 ]
George Timoshenko commented on HARMONY-1802:
--------------------------------------------
The testcase for the problem of unresolvable exception types.
Scenario is the same:
- compile
- remove CustomE
- run with '-Xem opt' key
=====
public class TestExc {
public static void main(String[] args) {
try {
if (false) {
CustomE e = new CustomE();
throw e;
}
} catch (CustomE e) {
System.out.println(e.getMessage());
}
}
}
class CustomE extends Exception {}
=====
> [drlvm][jit] Jitrino.OPT does not handle unresolved method parameters properly
> ------------------------------------------------------------------------------
>
> Key: HARMONY-1802
> URL: http://issues.apache.org/jira/browse/HARMONY-1802
> Project: Harmony
> Issue Type: Bug
> Reporter: Mikhail Fursov
>
> Jitrino.OPT does not handle unresolved method parameters properly. Here is the testcase.
> compile this code:
> public class Test {
> public static void main(String[] args) {
> foo(null);
> }
> static void foo(X x) {}
> }
> class X {
> }
> delete X.class file and run the test with -Xem:opt cmdline option.
> The same problem occurs if class X is exception handler parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|