1. 28 2月, 2011 1 次提交
  2. 27 2月, 2011 1 次提交
  3. 25 2月, 2011 1 次提交
  4. 19 2月, 2011 1 次提交
  5. 17 2月, 2011 3 次提交
  6. 12 2月, 2011 1 次提交
  7. 11 2月, 2011 2 次提交
  8. 10 2月, 2011 2 次提交
  9. 09 2月, 2011 3 次提交
  10. 08 2月, 2011 3 次提交
    • S
      7014851: Remove unused parallel compaction code · 2b4c6b63
      stefank 提交于
      Summary: Removed.
      Reviewed-by: jcoomes, brutisso
      2b4c6b63
    • Y
      6912621: iCMS: Error: assert(_markBitMap.isMarked(addr + 1),"Missing Printezis bit?") · 251d4f53
      ysr 提交于
      Summary: Fix block_size_if_printezis_bits() so it does not expect the bits, only uses them when available. Fix block_size_no_stall() so it does not stall when the bits are missing such cases, letting the caller deal with zero size returns. Constant pool cache oops do not need to be unparsable or conc_unsafe after their klass pointer is installed. Some cosmetic clean-ups and some assertion checking for conc-usafety which, in the presence of class file redefinition, has no a-priori time boundedness, so all GCs must be able to safely deal with putatively conc-unsafe objects in a stop-world pause.
      Reviewed-by: jmasa, johnc
      251d4f53
    • C
      6472925: OutOfMemoryError fails to generate stack trace as it now ought · 7f04da98
      coleenp 提交于
      Summary: Print an additional message for OOM during stack trace printing
      Reviewed-by: dholmes, phh, acorn, kamg, dcubed
      7f04da98
  11. 04 2月, 2011 3 次提交
  12. 03 2月, 2011 4 次提交
    • C
      7012088: jump to 0 address because of lack of memory ordering in SignatureHandlerLibrary::add · dd877cb2
      coleenp 提交于
      Summary: Write method signature handler under lock to prevent race with growable array resizing
      Reviewed-by: dsamersoff, dholmes
      dd877cb2
    • K
      6766644: Redefinition of compiled method fails with assertion "Can not load... · ffd09be1
      kamg 提交于
      6766644: Redefinition of compiled method fails with assertion "Can not load classes with the Compiler thread"
      Summary: Defer posting events from the compiler thread: use service thread
      Reviewed-by: coleenp, dholmes, never, dcubed
      ffd09be1
    • J
      6923430: G1: assert(res != 0,"This should have worked.") · a2031db9
      johnc 提交于
      7007446: G1: expand the heap with a single step, not one region at a time
      Summary: Changed G1CollectedHeap::expand() to expand the committed space by calling VirtualSpace::expand_by() once rather than for every region in the expansion amount. This allows the success or failure of the expansion to be determined before creating any heap regions. Introduced a develop flag G1ExitOnExpansionFailure (false by default) that, when true, will exit the VM if the expansion of the committed space fails. Finally G1CollectedHeap::expand() returns a status back to it's caller so that the caller knows whether to attempt the allocation.
      Reviewed-by: brutisso, tonyp
      a2031db9
    • B
      7016023: Enable building ARM and PPC from src/closed repository · fab382b2
      bobv 提交于
      Reviewed-by: dholmes, bdelsart
      fab382b2
  13. 02 2月, 2011 1 次提交
    • C
      6588413: Use -fvisibility=hidden for gcc compiles · e02b7391
      coleenp 提交于
      Summary: Add option for gcc 4 and above, define JNIEXPORT and JNIIMPORT to visibility=default, add for jio_snprintf and others since -fvisibility=hidden overrides --version-script definitions.
      Reviewed-by: kamg, never
      e02b7391
  14. 01 2月, 2011 1 次提交
  15. 02 2月, 2011 1 次提交
  16. 01 2月, 2011 1 次提交
    • T
      7014679: G1: deadlock during concurrent cleanup · a54411a3
      tonyp 提交于
      Summary: There's a potential deadlock between the concurrent cleanup thread and the GC workers that are trying to allocate and waiting for more free regions to be made available.
      Reviewed-by: iveresov, jcoomes
      a54411a3
  17. 28 1月, 2011 1 次提交
  18. 26 1月, 2011 2 次提交
    • T
      7014261: G1: RSet-related failures · 1498a56a
      tonyp 提交于
      Summary: A race between the concurrent cleanup thread and the VM thread while it is processing the "expanded sparse table list" causes both threads to try to free the same sparse table entry and either causes one of the threads to fail or leaves the entry in an inconsistent state. The solution is purge all entries on the expanded list that correspond go regions that are being cleaned up.
      Reviewed-by: brutisso, johnc
      1498a56a
    • J
      6608385: G1: need to support parallel reference processing · 477822c8
      johnc 提交于
      Summary: Implement support for ParallelRefProcEnabled in the reference processing that takes place at the end of G1 concurrent marking.
      Reviewed-by: tonyp, ysr
      477822c8
  19. 25 1月, 2011 2 次提交
  20. 22 1月, 2011 2 次提交
  21. 21 1月, 2011 1 次提交
  22. 20 1月, 2011 3 次提交
    • T
      6977804: G1: remove the zero-filling thread · 0ed267ef
      tonyp 提交于
      Summary: This changeset removes the zero-filling thread from G1 and collapses the two free region lists we had before (the "free" and "unclean" lists) into one. The new free list uses the new heap region sets / lists abstractions that we'll ultimately use it to keep track of all regions in the heap. A heap region set was also introduced for the humongous regions. Finally, this change increases the concurrency between the thread that completes freeing regions (after a cleanup pause) and the rest of the system (before we'd have to wait for said thread to complete before allocating a new region). The changest also includes a lot of refactoring and code simplification.
      Reviewed-by: jcoomes, johnc
      0ed267ef
    • K
      7012505: BreakpointWithFullGC.sh fails with Internal Error (src/share/vm/oops/methodOop.cpp:220) · 0457abfb
      kamg 提交于
      Summary: Rebuild breakpoint cache at gc_epilogue instead of during oops_do
      Reviewed-by: dcubed, ysr, coleenp
      0457abfb
    • N
      7013008: 2/3 assert(method == NULL || check_method(method, bcp)) failed: bcp must point into method · 2ec2714d
      never 提交于
      Summary: The Relocator should pass a NULL methodOop when rewriting since its resource array can never contain breakpoints.
      Reviewed-by: dcubed, kvn, coleenp
      2ec2714d