1. 20 10月, 2010 1 次提交
    • T
      Merge · e6326126
      twisti 提交于
      e6326126
  2. 19 10月, 2010 3 次提交
  3. 18 10月, 2010 1 次提交
  4. 16 10月, 2010 2 次提交
  5. 15 10月, 2010 4 次提交
  6. 14 10月, 2010 2 次提交
    • R
      Merge · 766034c2
      roland 提交于
      766034c2
    • T
      Merge · 27925402
      twisti 提交于
      27925402
  7. 13 10月, 2010 6 次提交
  8. 12 10月, 2010 2 次提交
  9. 11 10月, 2010 1 次提交
  10. 09 10月, 2010 1 次提交
    • J
      Merge · 7d9eea06
      jcoomes 提交于
      7d9eea06
  11. 08 10月, 2010 4 次提交
  12. 07 10月, 2010 2 次提交
  13. 06 10月, 2010 2 次提交
  14. 05 10月, 2010 5 次提交
  15. 02 10月, 2010 4 次提交
    • T
      Added tag hs20-b01 for changeset 5511edd5d719 · b3f0ab02
      trims 提交于
      b3f0ab02
    • C
      Added tag jdk7-b112 for changeset 5511edd5d719 · cee5486c
      cl 提交于
      cee5486c
    • T
      6980838: G1: guarantee(false) failed: thread has an unexpected active value in its SATB queue · acd6a8e3
      tonyp 提交于
      Summary: Under certain circumstances a safepoint could happen between a JavaThread object being created and that object being added to the Java threads list. This could cause the active field of that thread's SATB queue to get out-of-sync with respect to the other Java threads. The solution is to activate the SATB queue, when necessary, before adding the thread to the Java threads list, not when the JavaThread object is created. The changeset also includes a small fix to rename the surrogate locker thread from "Surrogate Locker Thread (CMS)" to "Surrogate Locker Thread (Concurrent GC)" since it's also used in G1.
      Reviewed-by: iveresov, ysr, johnc, jcoomes
      acd6a8e3
    • J
      Merge · 813d5b79
      johnc 提交于
      813d5b79