harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Ozhdikhin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1942) [drlvm] Back-branch polling TLS offset is incorrect. Stability and performance fix
Date Fri, 27 Oct 2006 06:17:18 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1942?page=comments#action_12445090 ] 
            
Pavel Ozhdikhin commented on HARMONY-1942:
------------------------------------------

To complete the patch, the change below should be applied as well (already committed).

Index: vm/jitrino/src/vm/VMInterface.cpp
===================================================================
--- vm/jitrino/src/vm/VMInterface.cpp	(revision 468248)
+++ vm/jitrino/src/vm/VMInterface.cpp	(working copy)
@@ -100,7 +100,7 @@
     DECL_HELPER_ITEM(ConvDtoI32),
     DECL_HELPER_ITEM(ConvDtoI64),
     DECL_HELPER_ITEM(EnableThreadSuspension),
-    DECL_HELPER_ITEM(GetSuspReqFlag),
+    DECL_HELPER_ITEM(GetTLSBase),
     DECL_HELPER_ITEM(MethodEntry),
     DECL_HELPER_ITEM(MethodExit),
     DECL_HELPER_ITEM(WriteBarrier),


> [drlvm] Back-branch polling TLS offset is incorrect. Stability and performance fix
> ----------------------------------------------------------------------------------
>
>                 Key: HARMONY-1942
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1942
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>         Assigned To: weldon washburn
>            Priority: Critical
>         Attachments: hy.diff, hy_2.diff
>
>
> The suspend flag's TLS offset used by JIT agorithms was incorrect after the latest merge
of TM.
> As the result every loop iteration BBP algorithm uses slow path.
> This patch 
> 1) Fixes the problem 
> 2) Adds new functionality to TM: the UDATA VMCALL hythread_tls_get_offset(hythread_tls_key_t
key)  method.
> 3) Removes jit_private data field from HyThread 
> 3) Fix JIT to always use allocation algorithm for TLS keys, not hardcoded values.

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