harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sian January (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HARMONY-5630) [classlib][pack200] Long.MAX_VALUE not decoded correctly
Date Tue, 25 Mar 2008 15:25:24 GMT

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

Sian January reassigned HARMONY-5630:
-------------------------------------

    Assignee: Sian January

> [classlib][pack200] Long.MAX_VALUE not decoded correctly
> --------------------------------------------------------
>
>                 Key: HARMONY-5630
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5630
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: All pack200
>            Reporter: Andrew Cornwall
>            Assignee: Sian January
>
> The value Long.MAX_VALUE appears not to be decoded correctly all the time. (Perhaps the
value's overflowing while being computed?) Here's a testcase:
> public class SimpleHelloWorld {
>     public static long long1 = -1;
>     public static long long2 = Long.MAX_VALUE;
>     public static void main(String args) {
>         System.out.println(long1 + long2);
>     }
> }
> I packed that with regular compression and then unpacked it. My BcBands.bcLongRef was
[0, 1] instead of  [-1, 9223372036854775807].
> I've got another test case (proprietary code) which causes BcBands.bcLongRef to be [.....,
-1, -1 ....]. I'll send that to Sian by email. That's how I detected this issue - the two
long refs were collapsed into one.

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


Mime
View raw message