harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1949) [drlvm][gc_cc] Refactoring TLS access in GC_CC.
Date Wed, 25 Oct 2006 13:28:25 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1949?page=comments#action_12444656 ] 
            
Ivan Volosyuk commented on HARMONY-1949:
----------------------------------------

Does frontier allocation still works? Why don't we disable it with 'return false' otherwise?

 Boolean gc_supports_frontier_allocation(unsigned *offset_of_current, unsigned *offset_of_limit)
{
     // Need additional support for object offset in native stubs.
-    *offset_of_current = field_offset(GC_Thread_Info, tls_current_free);
-    *offset_of_limit = field_offset(GC_Thread_Info, tls_current_cleaned);
+    *offset_of_current = tls_offset_current;
+    *offset_of_limit = tls_offset_clean;
     return true;
     ^^^ here

> [drlvm][gc_cc] Refactoring TLS access in GC_CC.
> -----------------------------------------------
>
>                 Key: HARMONY-1949
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1949
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>         Assigned To: weldon washburn
>         Attachments: gc_cc.diff
>
>
> This patch changes the way GC requests TLS data: Instead of asking VM  GC calls to TM
directly.
> After the patch is applied GC is able to report static offsets for all TLS fields it
uses to JIT

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

        

Mime
View raw message