You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Xiaoming Gu (JIRA)" <ji...@apache.org> on 2008/11/20 06:12:44 UTC
[jira] Created: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
[drlvm][jit] Incorrect generated instruction in peephole opt for MOV
--------------------------------------------------------------------
Key: HARMONY-6024
URL: https://issues.apache.org/jira/browse/HARMONY-6024
Project: Harmony
Issue Type: Bug
Environment: IA32 Windows
Reporter: Xiaoming Gu
In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
MOV opnd, opnd2 MOV opnd3, opnd2
MOV opnd3, opnd =>
The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
Posted by "Xiaoming Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoming Gu updated HARMONY-6024:
---------------------------------
Description:
In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
MOV opnd, opnd2
MOV opnd3, opnd
=>
MOV opnd3, opnd2
The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
was:
In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
MOV opnd, opnd2 MOV opnd3, opnd2
MOV opnd3, opnd =>
The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
> [drlvm][jit] Incorrect generated instruction in peephole opt for MOV
> --------------------------------------------------------------------
>
> Key: HARMONY-6024
> URL: https://issues.apache.org/jira/browse/HARMONY-6024
> Project: Harmony
> Issue Type: Bug
> Environment: IA32 Windows
> Reporter: Xiaoming Gu
> Attachments: H6024-V1.patch
>
>
> In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
> MOV opnd, opnd2
> MOV opnd3, opnd
> =>
> MOV opnd3, opnd2
> The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
Posted by "Xiaoming Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoming Gu updated HARMONY-6024:
---------------------------------
Attachment: H6024-V1.patch
This message is for V1 patch.
Some code is added to generate pseudo copy instruction if the original two MOV are both pseudo.
(The patch for H6016 is included.)
> [drlvm][jit] Incorrect generated instruction in peephole opt for MOV
> --------------------------------------------------------------------
>
> Key: HARMONY-6024
> URL: https://issues.apache.org/jira/browse/HARMONY-6024
> Project: Harmony
> Issue Type: Bug
> Environment: IA32 Windows
> Reporter: Xiaoming Gu
> Attachments: H6024-V1.patch
>
>
> In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
> MOV opnd, opnd2 MOV opnd3, opnd2
> MOV opnd3, opnd =>
> The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
Posted by "Xiaoming Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649275#action_12649275 ]
Xiaoming Gu commented on HARMONY-6024:
--------------------------------------
The patch is included into the patch for H6023.
> [drlvm][jit] Incorrect generated instruction in peephole opt for MOV
> --------------------------------------------------------------------
>
> Key: HARMONY-6024
> URL: https://issues.apache.org/jira/browse/HARMONY-6024
> Project: Harmony
> Issue Type: Bug
> Environment: IA32 Windows
> Reporter: Xiaoming Gu
> Attachments: H6024-V1.patch
>
>
> In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
> MOV opnd, opnd2
> MOV opnd3, opnd
> =>
> MOV opnd3, opnd2
> The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
Posted by "Xiaoming Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoming Gu updated HARMONY-6024:
---------------------------------
Comment: was deleted
> [drlvm][jit] Incorrect generated instruction in peephole opt for MOV
> --------------------------------------------------------------------
>
> Key: HARMONY-6024
> URL: https://issues.apache.org/jira/browse/HARMONY-6024
> Project: Harmony
> Issue Type: Bug
> Environment: IA32 Windows
> Reporter: Xiaoming Gu
> Attachments: H6024-V1.patch
>
>
> In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
> MOV opnd, opnd2
> MOV opnd3, opnd
> =>
> MOV opnd3, opnd2
> The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-6024) [drlvm][jit] Incorrect generated
instruction in peephole opt for MOV
Posted by "Xiaoming Gu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649276#action_12649276 ]
Xiaoming Gu commented on HARMONY-6024:
--------------------------------------
The patch is included into the patch for H6023. (https://issues.apache.org/jira/browse/HARMONY-6023)
> [drlvm][jit] Incorrect generated instruction in peephole opt for MOV
> --------------------------------------------------------------------
>
> Key: HARMONY-6024
> URL: https://issues.apache.org/jira/browse/HARMONY-6024
> Project: Harmony
> Issue Type: Bug
> Environment: IA32 Windows
> Reporter: Xiaoming Gu
> Attachments: H6024-V1.patch
>
>
> In the case 1 of peephole opt for MOV in Ia32PeepHole.cpp, the optimization is like following:
> MOV opnd, opnd2
> MOV opnd3, opnd
> =>
> MOV opnd3, opnd2
> The bug is the new MOV instruction is always generated by "newInst" even the original MOV instructions are both pseudo copy, which will cause an assertion error later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.