- 12 11月, 2010 2 次提交
- 11 11月, 2010 1 次提交
-
-
由 trims 提交于
-
- 05 11月, 2010 3 次提交
- 03 11月, 2010 1 次提交
-
-
由 iveresov 提交于
Summary: Turn CDS off if compressed oops is on Reviewed-by: ysr, kvn, jcoomes, phh
-
- 02 11月, 2010 1 次提交
-
-
由 jcoomes 提交于
-
- 29 10月, 2010 2 次提交
- 27 10月, 2010 3 次提交
- 26 10月, 2010 1 次提交
-
-
由 acorn 提交于
-
- 24 10月, 2010 1 次提交
-
-
由 ysr 提交于
Summary: Deprecated HandlePromotionFailure, removing the ability to turn off that feature, did away with one epoch look-ahead when deciding if a scavenge is likely to fail, relying on current data. Reviewed-by: jmasa, johnc, poonam
-
- 23 10月, 2010 1 次提交
-
-
由 acorn 提交于
Summary: reduce complexity by factoring synchronizer.cpp Reviewed-by: dholmes, never, coleenp
-
- 22 10月, 2010 2 次提交
-
-
由 ysr 提交于
Summary: Closed a timing hole during which concurrent full gc requests can be missed. The hole can increase the latency of the response to a full gc request by up to the value of CMSWaitDuration. If CMSWaitDuration=0 is, as currently, interpreted as an unbounded wait, suitable in certain tuning scenarios, the application can potentially hang. Made two obscure tunables, including CMSWaitDuration, manageable. Reviewed-by: jcoomes, tonyp
-
由 cl 提交于
-
- 21 10月, 2010 3 次提交
- 20 10月, 2010 1 次提交
-
-
由 iveresov 提交于
Summary: Temporarily fix to disable compressed oops with CDS Reviewed-by: dholmes, twisti, kvn, never
-
- 19 10月, 2010 1 次提交
-
-
由 never 提交于
-
- 17 10月, 2010 1 次提交
-
-
由 tonyp 提交于
Summary: There is a race between the concurrent refinement threads and the humongous object allocation that can cause the concurrent refinement threads to corrupt the part of the BOT that it is being initialized by the humongous object allocation operation. The solution is to do the humongous object allocation in careful steps to ensure that the concurrent refinement threads always have a consistent view over the BOT, region contents, and top. The fix includes some very minor tidying up in sparsePRT. Reviewed-by: jcoomes, johnc, ysr
-
- 19 10月, 2010 1 次提交
-
-
由 johnc 提交于
6988458: G1: assert(mr.end() <= _cm->finger()) failed: otherwise the region shouldn't be on the stack Summary: The changes from 6941395 did not clear the CMTask::_aborted_region fields when concurrent marking aborted because of overflow. As a result, the next time around we could see a memory region whose start address was above the global finger and the assertion tripped. Moved the clearing of the aborted regions to ConcurrentMark::clear_marking_state, which is executed on all of the exit paths. Reviewed-by: tonyp, ysr, jmasa
-
- 16 10月, 2010 3 次提交
- 15 10月, 2010 5 次提交
- 14 10月, 2010 3 次提交
- 13 10月, 2010 4 次提交
-
-
由 acorn 提交于
-
由 roland 提交于
Summary: fixes sparc only assert failure following 6972540 Reviewed-by: never
-
由 twisti 提交于
Reviewed-by: never, jrose
-
由 iveresov 提交于
Summary: Fix compare-and-swap intrinsic problem with G1 post-barriers and issue with branch ranges in G1 stubs on sparc Reviewed-by: never, kvn
-