Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <18825291.1195174723275.JavaMail.jira@brutus>
Date: Thu, 15 Nov 2007 16:58:43 -0800 (PST)
From: "Ilya Berezhniuk (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-5098) Support for uncompressed heap
 references in gc
In-Reply-To: <18382219.1194546530567.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542920 ] 

Ilya Berezhniuk commented on HARMONY-5098:
------------------------------------------

Now I see that obj_info is used for storing current representation of reference - i.e. raw pointers for uncompressed mode.
We can compress these pointers, but we will be forced to do this even in uncompressed mode - the strange situation.

Object layout can be changed so that obj_info will be raw pointer (it will require proper alignment and padding).
On the other side, it is not good too. Such changes depreciate compressed vtables; also such changes in object layout agreement will affect VM code essentially, and will also affect other GCs.

So I agree, using compression for these pointers is much easier to implement; we can check performance penalty.


> Support for uncompressed heap references in gc
> ----------------------------------------------
>
>                 Key: HARMONY-5098
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5098
>             Project: Harmony
>          Issue Type: New Feature
>          Components: DRLVM
>            Reporter: Rana Dasgupta
>         Attachments: H5098.uncompRef.patch, uncompress.patch
>
>
> JIRA issue for gc changes to support uncompressed 64 bit references

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