You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "George Timoshenko (JIRA)" <ji...@apache.org> on 2008/01/18 11:49:35 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&focusedCommentId=12560336#action_12560336 ]
George Timoshenko commented on HARMONY-3584:
--------------------------------------------
As the patch is still not committed
it should be updated to take https://issues.apache.org/jira/browse/HARMONY-5399 changes into account.
> [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
> Assignee: Mikhail Fursov
> Priority: Minor
> Attachments: arraycopy.patch, arraycopy_pass.patch, HARMONY-3584_arraycopy_up_to_date.patch, HARMONY-3584_arraycopy_up_to_date2.patch, intrinsic_patch.patch
>
>
> 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.