1. 03 12月, 2010 1 次提交
  2. 02 12月, 2010 1 次提交
  3. 01 12月, 2010 2 次提交
    • I
      6985015: C1 needs to support compressed oops · 7e8f9e32
      iveresov 提交于
      Summary: This change implements compressed oops for C1 for x64 and sparc. The changes are mostly on the codegen level, with a few exceptions when we do access things outside of the heap that are uncompressed from the IR. Compressed oops are now also enabled with tiered.
      Reviewed-by: twisti, kvn, never, phh
      7e8f9e32
    • T
      7001363: java/dyn/InvokeDynamic should not be a well-known class in the JVM · 535984b8
      twisti 提交于
      Summary: Because of the removal of language support, the JDK 7 API for JSR 292 no longer includes a public class named java/dyn/InvokeDynamic.
      Reviewed-by: jrose, kvn
      535984b8
  4. 24 11月, 2010 1 次提交
  5. 23 11月, 2010 1 次提交
  6. 19 11月, 2010 1 次提交
  7. 17 11月, 2010 3 次提交
  8. 13 11月, 2010 1 次提交
  9. 12 11月, 2010 1 次提交
  10. 10 11月, 2010 3 次提交
  11. 07 11月, 2010 1 次提交
  12. 06 11月, 2010 3 次提交
  13. 05 11月, 2010 1 次提交
  14. 03 11月, 2010 2 次提交
  15. 31 10月, 2010 3 次提交
  16. 29 10月, 2010 1 次提交
  17. 28 10月, 2010 2 次提交
  18. 27 10月, 2010 1 次提交
  19. 24 10月, 2010 1 次提交
  20. 23 10月, 2010 1 次提交
  21. 22 10月, 2010 3 次提交
  22. 21 10月, 2010 1 次提交
  23. 20 10月, 2010 2 次提交
  24. 19 10月, 2010 1 次提交
  25. 17 10月, 2010 1 次提交
    • T
      6991377: G1: race between concurrent refinement and humongous object allocation · a9a0cccb
      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
      a9a0cccb
  26. 19 10月, 2010 1 次提交
    • J
      6988458: G1: assert(mr.end() <= _cm->finger()) failed: otherwise the region... · f0680241
      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
      f0680241