1. 07 5月, 2013 1 次提交
  2. 13 3月, 2013 1 次提交
  3. 24 1月, 2013 1 次提交
  4. 28 11月, 2012 1 次提交
  5. 30 10月, 2012 1 次提交
  6. 02 9月, 2012 1 次提交
  7. 25 7月, 2012 1 次提交
  8. 09 5月, 2012 1 次提交
  9. 17 6月, 2011 1 次提交
  10. 13 5月, 2011 1 次提交
  11. 12 4月, 2011 1 次提交
  12. 08 4月, 2011 1 次提交
    • J
      7009266: G1: assert(obj->is_oop_or_null(true )) failed: Error · 6f87c7dd
      johnc 提交于
      Summary: A referent object that is only weakly reachable at the start of concurrent marking but is re-attached to the strongly reachable object graph during marking may not be marked as live. This can cause the reference object to be processed prematurely and leave dangling pointers to the referent object. Implement a read barrier for the java.lang.ref.Reference::referent field by intrinsifying the Reference.get() method, and intercepting accesses though JNI, reflection, and Unsafe, so that when a non-null referent object is read it is also logged in an SATB buffer.
      Reviewed-by: kvn, iveresov, never, tonyp, dholmes
      6f87c7dd
  13. 19 3月, 2011 1 次提交
  14. 24 11月, 2010 1 次提交
  15. 14 6月, 2010 1 次提交
  16. 28 5月, 2010 1 次提交
  17. 12 5月, 2010 1 次提交
  18. 30 4月, 2010 1 次提交
  19. 15 4月, 2010 1 次提交
  20. 30 3月, 2010 1 次提交
  21. 13 2月, 2010 1 次提交
    • K
      6926048: Improve Zero performance · d6d88011
      kvn 提交于
      Summary: Make Zero figure out result types in a similar way to C++ interpreter implementation.
      Reviewed-by: kvn
      Contributed-by: gbenson@redhat.com
      d6d88011
  22. 06 1月, 2010 1 次提交
  23. 27 11月, 2009 1 次提交
  24. 14 10月, 2009 1 次提交