Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <30265018.1187143291052.JavaMail.jira@brutus>
Date: Tue, 14 Aug 2007 19:01:31 -0700 (PDT)
From: "Xiao-Feng Li (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-3584) [drlvm][jit][opt] arraycopy folding
 implementation in guarded manner
In-Reply-To: <14019831.1175855317419.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xiao-Feng Li updated HARMONY-3584:
----------------------------------

    Priority: Critical  (was: Minor)

I raised the priority of this issue. It's a blocker to generational mode GC collection. 

> [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: Critical
>
> 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.