Searched hist:1358 (Results 1 - 3 of 3) sorted by relevance
| /openjdk10/hotspot/src/share/vm/runtime/ | ||
| H A D | mutexLocker.cpp | diff 1358:72f725c5a7be Sun Apr 04 22:19:00 MDT 2010 tonyp 6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() Summary: Calling the methods region_stack_push() and region_stack_pop() concurrent is not MT-safe. The assumption is that we will only call region_stack_push() during a GC pause and region_stack_pop() during marking. Unfortunately, we also call region_stack_push() during marking which seems to be introducing subtle marking failures. This change introduces lock-based methods for pushing / popping to be called during marking. Reviewed-by: iveresov, johnc |
| H A D | mutexLocker.hpp | diff 1358:72f725c5a7be Sun Apr 04 22:19:00 MDT 2010 tonyp 6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() Summary: Calling the methods region_stack_push() and region_stack_pop() concurrent is not MT-safe. The assumption is that we will only call region_stack_push() during a GC pause and region_stack_pop() during marking. Unfortunately, we also call region_stack_push() during marking which seems to be introducing subtle marking failures. This change introduces lock-based methods for pushing / popping to be called during marking. Reviewed-by: iveresov, johnc |
| /openjdk10/make/ | ||
| H A D | CompileJavaModules.gmk | diff 1358:381c5a34a4af Mon Feb 16 10:02:00 MST 2015 serb 8039269: images/cursors should not be in ${java.home}/lib Reviewed-by: mchung, alanb, erikj |
Completed in 64 milliseconds