You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Sergey Kuksenko (JIRA)" <ji...@apache.org> on 2007/04/24 15:28:37 UTC
[jira] Created: (HARMONY-3745) [drlvm][gc][jit] server.emconf
should be unified both for gc_cc and gc_gen
[drlvm][gc][jit] server.emconf should be unified both for gc_cc and gc_gen
--------------------------------------------------------------------------
Key: HARMONY-3745
URL: https://issues.apache.org/jira/browse/HARMONY-3745
Project: Harmony
Issue Type: Improvement
Components: DRLVM
Reporter: Sergey Kuksenko
Currently, it is impossible to use -Xem:server mode in case of gc_gen turn on.
server.emconf should be modified for gc_gen usage.
Modification is simple -change all "gc_cc" substrings into "gc_gen". But it is more convinient to have unified emconf file in both cases.
All gc versions dependences are related to allocation helpers inline.
1) setup class name where allocation helpers are existed.
-XDjit.SD2_OPT.arg.optimizer.inline_helpers.newObj_className=org/apache/harmony/drlvm/gc_cc/GCHelper
gc_cc's helpers are in "gc_cc" package and gc_gen's in "gc_gen" respectively.
Usage "gc" package will solve problem here.
2) other two prorties set up which class from which jar-file should be used.
-Dvm.components.gc_cc.startupclass=org.apache.harmony.drlvm.gc_cc.GCHelper
-XDvm.component.classpath.gc_cc=gc_cc.jar
Storing such properties in emconf file is a source of misconfigurations and errors.
Component related properties should be set at moment of library initialization by the library itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-3745) [drlvm][gc][jit] server.emconf
should be unified both for gc_cc and gc_gen
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikhail Fursov resolved HARMONY-3745.
-------------------------------------
Resolution: Won't Fix
Assignee: Mikhail Fursov
Every GC implementation is allowed to have a set of specific options that affect performance.
The 'server' mode is not default mode and oriented to performance. The 'server.emconf' file is a configuration file for 'server' mode that contains all options specific for active components. So, instead of unifying all of options between different GC implementation (in general it's impossible) it's better to support different EM configuration files if needed.
> [drlvm][gc][jit] server.emconf should be unified both for gc_cc and gc_gen
> --------------------------------------------------------------------------
>
> Key: HARMONY-3745
> URL: https://issues.apache.org/jira/browse/HARMONY-3745
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Sergey Kuksenko
> Assignee: Mikhail Fursov
>
> Currently, it is impossible to use -Xem:server mode in case of gc_gen turn on.
> server.emconf should be modified for gc_gen usage.
> Modification is simple -change all "gc_cc" substrings into "gc_gen". But it is more convinient to have unified emconf file in both cases.
> All gc versions dependences are related to allocation helpers inline.
> 1) setup class name where allocation helpers are existed.
> -XDjit.SD2_OPT.arg.optimizer.inline_helpers.newObj_className=org/apache/harmony/drlvm/gc_cc/GCHelper
> gc_cc's helpers are in "gc_cc" package and gc_gen's in "gc_gen" respectively.
> Usage "gc" package will solve problem here.
> 2) other two prorties set up which class from which jar-file should be used.
> -Dvm.components.gc_cc.startupclass=org.apache.harmony.drlvm.gc_cc.GCHelper
> -XDvm.component.classpath.gc_cc=gc_cc.jar
> Storing such properties in emconf file is a source of misconfigurations and errors.
> Component related properties should be set at moment of library initialization by the library itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HARMONY-3745) [drlvm][gc][jit] server.emconf
should be unified both for gc_cc and gc_gen
Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491283 ]
Mikhail Fursov commented on HARMONY-3745:
-----------------------------------------
The problem is where to keep Java helper's classes and who will add them into bootstrap classpath.
Today we keep GC_GEN and GC_CC Java classes in separate JARs and both of them are in bootstrap classpath.
> [drlvm][gc][jit] server.emconf should be unified both for gc_cc and gc_gen
> --------------------------------------------------------------------------
>
> Key: HARMONY-3745
> URL: https://issues.apache.org/jira/browse/HARMONY-3745
> Project: Harmony
> Issue Type: Improvement
> Components: DRLVM
> Reporter: Sergey Kuksenko
>
> Currently, it is impossible to use -Xem:server mode in case of gc_gen turn on.
> server.emconf should be modified for gc_gen usage.
> Modification is simple -change all "gc_cc" substrings into "gc_gen". But it is more convinient to have unified emconf file in both cases.
> All gc versions dependences are related to allocation helpers inline.
> 1) setup class name where allocation helpers are existed.
> -XDjit.SD2_OPT.arg.optimizer.inline_helpers.newObj_className=org/apache/harmony/drlvm/gc_cc/GCHelper
> gc_cc's helpers are in "gc_cc" package and gc_gen's in "gc_gen" respectively.
> Usage "gc" package will solve problem here.
> 2) other two prorties set up which class from which jar-file should be used.
> -Dvm.components.gc_cc.startupclass=org.apache.harmony.drlvm.gc_cc.GCHelper
> -XDvm.component.classpath.gc_cc=gc_cc.jar
> Storing such properties in emconf file is a source of misconfigurations and errors.
> Component related properties should be set at moment of library initialization by the library itself.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.