Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <27034658.1182163466284.JavaMail.jira@brutus>
Date: Mon, 18 Jun 2007 03:44:26 -0700 (PDT)
From: "Mikhail Fursov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
 in lazy resolution mode with JET
In-Reply-To: <4849017.1180623075829.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-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Fursov closed HARMONY-4016.
-----------------------------------


> [drlvm][jit] gc.Mark fails when run in lazy resolution mode with JET
> --------------------------------------------------------------------
>
>                 Key: HARMONY-4016
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4016
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Mikhail Fursov
>         Attachments: lazy_fix.diff, lazy_fix2.diff, lazy_fix3.diff, lazy_fix4.diff
>
>
> I've found that gc.Mark fails when lazy resolution mode is on.
> the reason is that all VM helpers for lazy mode do not protect managed operands and these operands become outdated when GC enumeration happens.

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