You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/03/28 08:36:32 UTC
[jira] Created: (HARMONY-3511) [drlvm][jit] redundant layer in
Jitrino interfaces removed
[drlvm][jit] redundant layer in Jitrino interfaces removed
----------------------------------------------------------
Key: HARMONY-3511
URL: https://issues.apache.org/jira/browse/HARMONY-3511
Project: Harmony
Issue Type: Improvement
Components: DRLVM
Reporter: Alexey Varlamov
There is an extra (double) abstraction layer in Jitrino to OPEN interfaces, as well as a lot of dead APIs and code.
These APIs should be removed to reduce a mess in class hierarchy, and make Jitrino code cleaner.
Most radical solution would be to use OPEN interfaces directly in Jitrino internals, but OPEN are C APIs and somewhat inconvenient / inconsistent in style to C++ object code. Compromise is to keep minimal C++ wrappers to OPEN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3511) [drlvm][jit] redundant layer in
Jitrino interfaces removed
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov resolved HARMONY-3511.
--------------------------------------
Resolution: Fixed
Applied at r525110.
> [drlvm][jit] redundant layer in Jitrino interfaces removed
> ----------------------------------------------------------
>
> Key: HARMONY-3511
> URL: https://issues.apache.org/jira/browse/HARMONY-3511
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assigned To: Alexey Varlamov
> Attachments: jit.intf.cleanup.diff, jit.ipf.diff
>
>
> There is an extra (double) abstraction layer in Jitrino to OPEN interfaces, as well as a lot of dead APIs and code.
> These APIs should be removed to reduce a mess in class hierarchy, and make Jitrino code cleaner.
> Most radical solution would be to use OPEN interfaces directly in Jitrino internals, but OPEN are C APIs and somewhat inconvenient / inconsistent in style to C++ object code. Compromise is to keep minimal C++ wrappers to OPEN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-3511) [drlvm][jit] redundant layer in
Jitrino interfaces removed
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-3511:
----------------------------------------
Assignee: Alexey Varlamov
> [drlvm][jit] redundant layer in Jitrino interfaces removed
> ----------------------------------------------------------
>
> Key: HARMONY-3511
> URL: https://issues.apache.org/jira/browse/HARMONY-3511
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Alexey Varlamov
> Assigned To: Alexey Varlamov
> Attachments: jit.intf.cleanup.diff, jit.ipf.diff
>
>
> There is an extra (double) abstraction layer in Jitrino to OPEN interfaces, as well as a lot of dead APIs and code.
> These APIs should be removed to reduce a mess in class hierarchy, and make Jitrino code cleaner.
> Most radical solution would be to use OPEN interfaces directly in Jitrino internals, but OPEN are C APIs and somewhat inconvenient / inconsistent in style to C++ object code. Compromise is to keep minimal C++ wrappers to OPEN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3511) [drlvm][jit] redundant layer in
Jitrino interfaces removed
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-3511:
-------------------------------------
Attachment: jit.ipf.diff
The IPF changes. + one need to uncomment VMInterface::areVTablePtrsCompressed() declaration in the first patch.
> [drlvm][jit] redundant layer in Jitrino interfaces removed
> ----------------------------------------------------------
>
> Key: HARMONY-3511
> URL: https://issues.apache.org/jira/browse/HARMONY-3511
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Alexey Varlamov
> Attachments: jit.intf.cleanup.diff, jit.ipf.diff
>
>
> There is an extra (double) abstraction layer in Jitrino to OPEN interfaces, as well as a lot of dead APIs and code.
> These APIs should be removed to reduce a mess in class hierarchy, and make Jitrino code cleaner.
> Most radical solution would be to use OPEN interfaces directly in Jitrino internals, but OPEN are C APIs and somewhat inconvenient / inconsistent in style to C++ object code. Compromise is to keep minimal C++ wrappers to OPEN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-3511) [drlvm][jit] redundant layer in
Jitrino interfaces removed
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov updated HARMONY-3511:
-------------------------------------
Attachment: jit.intf.cleanup.diff
Attached diff removes the extra layer, cleans dead APIs and classes, reduces some duplicate enums.
> [drlvm][jit] redundant layer in Jitrino interfaces removed
> ----------------------------------------------------------
>
> Key: HARMONY-3511
> URL: https://issues.apache.org/jira/browse/HARMONY-3511
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Alexey Varlamov
> Attachments: jit.intf.cleanup.diff
>
>
> There is an extra (double) abstraction layer in Jitrino to OPEN interfaces, as well as a lot of dead APIs and code.
> These APIs should be removed to reduce a mess in class hierarchy, and make Jitrino code cleaner.
> Most radical solution would be to use OPEN interfaces directly in Jitrino internals, but OPEN are C APIs and somewhat inconvenient / inconsistent in style to C++ object code. Compromise is to keep minimal C++ wrappers to OPEN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.