You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mikhail Fursov (JIRA)" <ji...@apache.org> on 2007/06/18 12:44:26 UTC
[jira] Resolved: (HARMONY-4016) [drlvm][jit] gc.Mark fails when run
in lazy resolution mode with JET
[ https://issues.apache.org/jira/browse/HARMONY-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov resolved HARMONY-4016.
-------------------------------------
Resolution: Fixed
Committed revision 548294
> [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.