1. 19 5月, 2010 3 次提交
  2. 18 5月, 2010 1 次提交
  3. 11 5月, 2010 1 次提交
  4. 06 5月, 2010 1 次提交
  5. 05 5月, 2010 1 次提交
  6. 04 5月, 2010 1 次提交
  7. 02 5月, 2010 1 次提交
  8. 01 5月, 2010 1 次提交
  9. 30 4月, 2010 2 次提交
  10. 29 4月, 2010 1 次提交
    • T
      6829193: JSR 292 needs to support SPARC · 9c88edc1
      twisti 提交于
      Summary: There are unimplemented portions of the hotspot code for method handles and invokedynamic specific to SPARC.
      Reviewed-by: kvn, never, jrose
      9c88edc1
  11. 27 4月, 2010 2 次提交
  12. 23 4月, 2010 2 次提交
  13. 19 4月, 2010 1 次提交
  14. 17 4月, 2010 1 次提交
  15. 16 4月, 2010 4 次提交
  16. 15 4月, 2010 2 次提交
  17. 09 4月, 2010 1 次提交
    • I
      6942223: c1 64 bit fixes · f06b82f4
      iveresov 提交于
      Summary: This fixes lir_cmp_l2i on x64 and sparc 64bit, and the debug info generation.
      Reviewed-by: never
      f06b82f4
  18. 08 4月, 2010 5 次提交
  19. 06 4月, 2010 3 次提交
    • T
      6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.") · 524b2dd2
      tonyp 提交于
      Summary: Make sure that two marking cycles do not overlap, i.e., a new one can only start after the concurrent marking thread finishes all its work. In the fix I piggy-back a couple of minor extra fixes: some general code reformatting for consistency (only around the code I modified), the removal of a field (G1CollectorPolicy::_should_initiate_conc_mark) which doesn't seem to be used at all (it's only set but never read), as well as moving the "is GC locker active" test earlier into the G1 pause / Full GC and using a more appropriate method for it.
      Reviewed-by: johnc, jmasa, jcoomes, ysr
      524b2dd2
    • T
      6940520: CodeCache::scavenge_root_nmethods_do must fix oop relocations · 04362522
      twisti 提交于
      Summary: ScavengeRootsInCode can lead to unfixed code-embedded oops.
      Reviewed-by: kvn, never
      04362522
    • T
      6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() · 1bf17034
      tonyp 提交于
      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
      1bf17034
  20. 03 4月, 2010 2 次提交
  21. 02 4月, 2010 1 次提交
  22. 01 4月, 2010 2 次提交
  23. 31 3月, 2010 1 次提交