Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <17203239.1160480666469.JavaMail.root@brutus>
Date: Tue, 10 Oct 2006 04:44:26 -0700 (PDT)
From: "Mikhail Fursov (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Commented: (HARMONY-1802) [drlvm][jit] Jitrino.OPT does not
 handle unresolved method parameters properly
In-Reply-To: <24454552.1160470039807.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HARMONY-1802?page=comments#action_12441128 ] 
            
Mikhail Fursov commented on HARMONY-1802:
-----------------------------------------

AFAIK there is no problem with return types.


> [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