Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8138888 Remove ExtendedOopClosure::apply_to_weak_ref_discovered_field
  3. JDK-8144908

Remove apply_to_weak_ref_discovered_field override for UpdateRSOopClosure

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: P4 P4
    • 9
    • 9
    • hotspot
    • None
    • gc
    • b103

      UpdateRSOopClosure is used to re-build the remembered sets after a G1 full GC. This is done after reference discovery and enqueuing (to the pending list) has been completed, so all discovered references have their next-field set. Before the full GC is started all references discovered by the concurrent-mark reference processor is clear to allow them to be discovered during the FullGC.

      So at the point of applying the UpdateRSOopClosure, no references should have their discovered field set but still be active (next == null). So overriding apply_to_weak_ref_discovered field to make sure the discovered field is treated doesn't have any effect. Either the discovered and next field are both set and the gets handled the normal way, or the discovered field is not set and there is no reason to handle it specially.

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

              Created:
              Updated:
              Resolved: