1. 09 8月, 2010 1 次提交
  2. 07 8月, 2010 1 次提交
    • J
      6930581: G1: assert(ParallelGCThreads > 1 || n_yielded() ==... · d0aa394b
      johnc 提交于
      6930581: G1: assert(ParallelGCThreads > 1 || n_yielded() == _hrrs->occupied(),"Should have yielded all the ..
      Summary: During RSet updating, when ParallelGCThreads is zero, references that point into the collection set are added directly the referenced region's RSet. This can cause the sparse table in the RSet to expand. RSet scanning and the "occupied" routine will then operate on different instances of the sparse table causing the assert to trip. This may also cause some cards added post expansion to be missed during RSet scanning. When ParallelGCThreads is non-zero such references are recorded on the "references to be scanned" queue and the card containing the reference is recorded in a dirty card queue for use in the event of an evacuation failure. Employ the parallel code in the serial case to avoid expanding the RSets of regions in the collection set.
      Reviewed-by: iveresov, ysr, tonyp
      d0aa394b
  3. 05 8月, 2010 1 次提交
    • T
      6963209: G1: remove the concept of abandoned pauses · e49283a2
      tonyp 提交于
      Summary: As part of 6944166 we disabled the concept of abandoned pauses (i.e., if the collection set is empty, we would still try to do a pause even if it is to update the RSets and scan the roots). This changeset removes the code and structures associated with abandoned pauses.
      Reviewed-by: iveresov, johnc
      e49283a2
  4. 22 7月, 2010 1 次提交
  5. 03 8月, 2010 1 次提交
    • J
      6814437: G1: remove the _new_refs array · 64711cc9
      johnc 提交于
      Summary: The per-worker _new_refs array is used to hold references that point into the collection set. It is populated during RSet updating and subsequently processed. In the event of an evacuation failure it processed again to recreate the RSets of regions in the collection set. Remove the per-worker _new_refs array by processing the references directly. Use a DirtyCardQueue to hold the cards containing the references so that the RSets of regions in the collection set can be recreated when handling an evacuation failure.
      Reviewed-by: iveresov, jmasa, tonyp
      64711cc9
  6. 31 7月, 2010 1 次提交
  7. 23 7月, 2010 1 次提交
  8. 20 7月, 2010 1 次提交
  9. 17 7月, 2010 2 次提交
  10. 16 7月, 2010 1 次提交
  11. 15 7月, 2010 3 次提交
  12. 13 7月, 2010 2 次提交
  13. 09 7月, 2010 1 次提交
  14. 08 7月, 2010 1 次提交
  15. 03 7月, 2010 3 次提交
  16. 02 7月, 2010 1 次提交
  17. 30 6月, 2010 1 次提交
  18. 29 6月, 2010 4 次提交
  19. 25 6月, 2010 1 次提交
  20. 24 6月, 2010 1 次提交
  21. 23 6月, 2010 2 次提交
  22. 22 6月, 2010 2 次提交
  23. 19 6月, 2010 1 次提交
  24. 16 6月, 2010 1 次提交
  25. 14 6月, 2010 1 次提交
  26. 13 6月, 2010 1 次提交
  27. 11 6月, 2010 1 次提交
  28. 10 6月, 2010 1 次提交
  29. 08 6月, 2010 1 次提交
    • J
      6953058: G1: A bigapp crashes with SIGSEGV in compiled code · 78ed4c5e
      johnc 提交于
      Summary: In C2's G1 post write barrier, the loads of the buffer and index fields from the DirtyCardQueue structure may be moved across a safepoint. Use the current value of "control" in the C2 IR to limit how far these loads can move.
      Reviewed-by: never, iveresov, kvn
      78ed4c5e