You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/03/13 12:13:09 UTC

[jira] Assigned: (HARMONY-3365) [drlvm][win64] Double.doubleToLongBits(double) produces incorrect results.

     [ https://issues.apache.org/jira/browse/HARMONY-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky reassigned HARMONY-3365:
------------------------------------------

    Assignee: Gregory Shimansky

> [drlvm][win64] Double.doubleToLongBits(double) produces incorrect results.
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-3365
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3365
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>         Assigned To: Gregory Shimansky
>            Priority: Critical
>         Attachments: H3365.patch
>
>
> While debugging DRLVM on WIN64 platform I've found that Double.doubleToLongBits(double) method produces incorect results and prevents some benchmarks to pass.
> Here is the test:
>     public static void main(String[] args) {
>         System.out.println(Double.doubleToLongBits(1));
>     }
> RI prints:
> 4607182418800017408
> Harmony (both JET and OPT)
> -3689348814741910324
> I think the cause is a problem in native stubs and calling conventions on windows in DRLVM.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.