You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Sergey Kuksenko (JIRA)" <ji...@apache.org> on 2007/08/14 10:11:30 UTC

[jira] Commented: (HARMONY-3584) [drlvm][jit][opt] arraycopy folding implementation in guarded manner

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

Sergey Kuksenko commented on HARMONY-3584:
------------------------------------------

I have only one comment here.
It would be better to insert the new optimization AFTER inliner. Because of of after inline and following type propogation we can get more detailed compile-time info about copying types.


> [drlvm][jit][opt] arraycopy folding implementation in guarded manner
> --------------------------------------------------------------------
>
>                 Key: HARMONY-3584
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3584
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: George Timoshenko
>            Priority: Minor
>
> the feature (arraycopy call replacement) can be done in the guarded manner. When the classes of the arrays are being checked at runtime. 
> (It is not obvious if it gives a performance effect or not). 
> when this approach (guarded arraycopy call "inlining") is being implemented this optimisation should be moved out from the translator and inserted (before inliner) into the HLO path as a separate optimisation. 

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