Mon, 30 Apr 2018 15:55:21 +0200 8202424: Metaspace: on chunk retirement, use correct lower limit on chunksize when adding blocks to free blocks list
stuefe [Mon, 30 Apr 2018 15:55:21 +0200] rev 49971
8202424: Metaspace: on chunk retirement, use correct lower limit on chunksize when adding blocks to free blocks list Reviewed-by: zgu, coleenp
Thu, 03 May 2018 06:20:37 -0700 8202584: de-problem list tools/javac/jvm/VerboseOutTest
vromero [Thu, 03 May 2018 06:20:37 -0700] rev 49970
8202584: de-problem list tools/javac/jvm/VerboseOutTest Reviewed-by: mcimadamore
Fri, 27 Apr 2018 15:00:04 -0400 8202447: Fix unloading_occurred to mean unloading_occurred
coleenp [Fri, 27 Apr 2018 15:00:04 -0400] rev 49969
8202447: Fix unloading_occurred to mean unloading_occurred Summary: nmethod unloading does not need to test for jvmti to set unloading_occurred, nor do we need to clean weak Klasses in metadata if unloading does not occur. Reviewed-by: sspitsyn, rehn
Thu, 03 May 2018 08:07:20 -0400 8199067: [REDO] NMT: Enhance thread stack tracking
zgu [Thu, 03 May 2018 08:07:20 -0400] rev 49968
8199067: [REDO] NMT: Enhance thread stack tracking Summary: Precise thread stack tracking on Linux and Windows Reviewed-by: stuefe, coleenp
Thu, 03 May 2018 14:10:08 +0200 8202021: Improve variable naming in ReferenceProcesso
tschatzl [Thu, 03 May 2018 14:10:08 +0200] rev 49967
8202021: Improve variable naming in ReferenceProcesso Reviewed-by: sangheki, sjohanss
Thu, 03 May 2018 14:09:39 +0200 8202018: Move card table clear before enqueuing pending references
tschatzl [Thu, 03 May 2018 14:09:39 +0200] rev 49966
8202018: Move card table clear before enqueuing pending references Summary: Move card table clearing in preparation of removal of the Reference enqueue phase. Reviewed-by: sangheki, sjohanss
Thu, 03 May 2018 14:09:21 +0200 8201640: Use _ref_processor_* member variables directly in G1CollectedHeap
tschatzl [Thu, 03 May 2018 14:09:21 +0200] rev 49965
8201640: Use _ref_processor_* member variables directly in G1CollectedHeap Reviewed-by: sjohanss
Thu, 03 May 2018 14:09:00 +0200 8201492: Properly implement non-contiguous generations for Reference discovery
tschatzl [Thu, 03 May 2018 14:09:00 +0200] rev 49964
8201492: Properly implement non-contiguous generations for Reference discovery Summary: Collectors like G1 implementing non-contiguous generations previously used an inexact but conservative area for discovery. Concurrent and STW reference processing could discover the same reference multiple times, potentially missing referents during evacuation. So these collectors had to take extra measures while concurrent marking/reference discovery has been running. This change makes discovery exact for G1 (and any collector using non-contiguous generations) so that concurrent discovery and STW discovery discover on strictly disjoint memory areas. This means that the mentioned situation can not occur any more, and extra work is not required any more too. Reviewed-by: kbarrett, sjohanss
(0) -30000 -10000 -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 tip