You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/01/31 07:20:06 UTC
[jira] Updated: (HARMONY-1802) [drlvm][jit] Jitrino.OPT does not
handle unresolved method parameters properly
[ https://issues.apache.org/jira/browse/HARMONY-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-1802:
-------------------------------------
Component/s: DRLVM
> [drlvm][jit] Jitrino.OPT does not handle unresolved method parameters properly
> ------------------------------------------------------------------------------
>
> Key: HARMONY-1802
> URL: https://issues.apache.org/jira/browse/HARMONY-1802
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Mikhail Fursov
> Assigned To: Geir Magnusson Jr
> Attachments: HARMONY-1802.diff
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.