Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <25359613.1201514374619.JavaMail.jira@brutus>
Date: Mon, 28 Jan 2008 01:59:34 -0800 (PST)
From: "Mikhail Fursov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-5425) [drlvm][jit][opt] Spillgen ignores
 intitial constrains sometimes
In-Reply-To: <20576231.1201255356049.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-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563102#action_12563102 ] 

Mikhail Fursov commented on HARMONY-5425:
-----------------------------------------

Alexey, the check I wrote was tested on 32-bit platform only. I do not included it into commit because of problems with it on EM64T.

> [drlvm][jit][opt] Spillgen ignores intitial constrains sometimes
> ----------------------------------------------------------------
>
>                 Key: HARMONY-5425
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5425
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Mikhail Fursov
>         Attachments: spill.diff
>
>
> I found that in some scenarios with high register pressure (I can't neither publish the sources or create a microtest) spillgen reassigns an operand from callee-save register to caller-save making its value invalid after a CALL
> The problem method was originally found in a method: org/apache/harmony/awt/gl/Crossing::intersectCubic
> I apply the patch that fixes the problem.

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