harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Ignatenko (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-3462) [dlrvm] new j.l.Class tracing model
Date Wed, 21 Mar 2007 12:47:32 GMT
[dlrvm] new j.l.Class tracing model

                 Key: HARMONY-3462
                 URL: https://issues.apache.org/jira/browse/HARMONY-3462
             Project: Harmony
          Issue Type: Improvement
          Components: DRLVM
            Reporter: Aleksey Ignatenko
         Attachments: new_class_registry_v7.patch

The jira introduces new model of j.l.Class referencing into drlvm.

The current model is:
all j.l.Classes (JLC) and j.l.Classloaders (JLCL) are enumerated as strong references inside
drlvm. It means that all JLC and JLCL are always reachable and we can not track any referencing
between classes and classloaders automatically by GC.

The new model is required by clas unloading (independent of class unloading design). Lets
name term "class registry" as -  JLCL refers to its JLC and JLC refer to their defining JLCL
(phisically via valid references). This requirement comes from the statement that classloader
and all classes loaded by it are to be unloaded at once. e.g. Robin-Salikh approach requires
that only JLCL are enumerated then JLC are to be traced automatically by GC (via references
in appropriate JLCL - right now there is no direct reference to JLC in JLCL and vice versa).

The patch new_class_registry_v7.patch introduces the direct references described above. Also,
it changes enumeration model: from now all JLC are traced via JLCL. JLC references are enumerated
as weak references now (to be updated by GC).
Also destination of m_loadedClasses and m_reportedClasses has changed. For now m_loadedClasses
is responsible for weak enumeration of all loaded UserDefined j.l.Classes and m_reportedClasses
is responsible for enumeration of all bootstrap classes and userdefined classes (untill they
are added to class registry)

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

View raw message