Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8138888

Remove ExtendedOopClosure::apply_to_weak_ref_discovered_field

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 10
    • 9
    • hotspot
    • None
    • gc
    • b21

    Description

      Currently the code for handling iteration of InstanceRefKlass oops in InstanceRefKlass::oop_oop_iterate_ref_processing_specialized has a special case for handling the discovered field. If the closure override apply_to_weak_ref_discovered_field() to return true, the closure will always be applied to the discovered field. The need for this special case is a bit unclear, it might have been added because otherwise the discovered field is only handled if the next field is non-NULL.

      I propose to remove apply_to_weak_ref_discovered_field() and also remove the check if next is NULL when handling the discovered field.

      Attachments

        Issue Links

          Activity

            People

              sjohanss Stefan Johansson
              sjohanss Stefan Johansson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: