You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Rebriy (JIRA)" <ji...@apache.org> on 2008/01/16 15:20:35 UTC

[jira] Commented: (HARMONY-3452) [drlvm][thread] os_thread_yield_other(), was apr_thread_yield_other does not actually do anything and needs removing

    [ https://issues.apache.org/jira/browse/HARMONY-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559506#action_12559506 ] 

Pavel Rebriy commented on HARMONY-3452:
---------------------------------------

The issue is seemed to be out-of-dated because these function is used in hythread (revision 612461).

> [drlvm][thread] os_thread_yield_other(), was apr_thread_yield_other does not actually do anything and needs removing
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3452
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3452
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: win/lin
>            Reporter: weldon washburn
>            Assignee: weldon washburn
>            Priority: Minor
>
> As far as I can tell, this procedure simply wastes cpu cycles.  I posted an email to harmony dev asking if anyone knows what this procedure does.  So far, no responses.  I also modified os_thread_yield_other() so that it immediately returns thus zero side effects.  Build and build test still passed the tests.  The task at hand is to remove this procedure and all its call sites.

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