harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoming Gu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-6211) [drlvm][jit] write barrier broken by H5826
Date Sat, 23 May 2009 10:37:45 GMT

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

Xiaoming Gu updated HARMONY-6211:

    Comment: was deleted

(was: This bug comes from a peephole optimization about ADD in H5826)

> [drlvm][jit] write barrier broken by H5826
> ------------------------------------------
>                 Key: HARMONY-6211
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6211
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows, IA32
>            Reporter: Xiaoming Gu
>         Attachments: H6211-V1.patch
> When using -XX:gc.generate_barrier=true, even a simple HelloWorld couldn't run correctly.
The bug is from an peephole optimization in H5826 which assumes no control flow branch in
the middle of a basic block. In fact, some CALL insts break the assumption and make the optimization
effective in wrong cases. Following is an example:
> I4: t5:ref:cls:java/lang/ref/ReferenceQueue =ADD t0:cls:java/lang/ref/Reference, t4(0):intptr
> I5: CALL t7(0):I_32 (AU:t0:cls:java/lang/ref/Reference, t5:ref:cls:java/lang/ref/ReferenceQueue,
t2:cls:java/lang/ref/ReferenceQueue) [bcmap:6]
> I6: t9:ref:cls:java/lang/Object =ADD t0:cls:java/lang/ref/Reference,t8(0):intptr
> I7: CALL t10(0):I_32 (AU:t0:cls:java/lang/ref/Reference,t9:ref:cls:java/lang/Object,t1:cls:java/lang/Object)
> I8: RET t11(0):int16

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

View raw message