1. 09 5月, 2013 1 次提交
  2. 25 4月, 2013 1 次提交
    • J
      8012715: G1: GraphKit accesses PtrQueue::_index as int but is size_t · 563afc34
      johnc 提交于
      Summary: In graphKit INT operations were generated to access PtrQueue::_index which has type size_t. This is 64 bit on 64-bit machines. No problems occur on little endian machines as long as the index fits into 32 bit, but on big endian machines the upper part is read, which is zero. This leads to unnecessary branches to the slow path in the runtime.
      Reviewed-by: twisti, johnc
      Contributed-by: NMartin Doerr <martin.doerr@sap.com>
      563afc34
  3. 27 3月, 2013 1 次提交
  4. 24 12月, 2012 1 次提交
  5. 20 12月, 2012 1 次提交
  6. 18 12月, 2012 1 次提交
  7. 28 11月, 2012 1 次提交
  8. 27 11月, 2012 1 次提交
  9. 09 10月, 2012 1 次提交
  10. 28 9月, 2012 1 次提交
  11. 02 9月, 2012 1 次提交
  12. 29 8月, 2012 1 次提交
  13. 25 7月, 2012 1 次提交
  14. 15 5月, 2012 1 次提交
  15. 08 2月, 2012 1 次提交
  16. 20 12月, 2011 1 次提交
  17. 07 12月, 2011 1 次提交
  18. 03 8月, 2011 1 次提交
  19. 05 5月, 2011 1 次提交
  20. 28 4月, 2011 1 次提交
  21. 26 4月, 2011 1 次提交
  22. 21 4月, 2011 1 次提交
  23. 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
  24. 06 4月, 2011 1 次提交
  25. 03 4月, 2011 1 次提交
  26. 22 3月, 2011 1 次提交
  27. 03 12月, 2010 1 次提交
  28. 24 11月, 2010 1 次提交
  29. 19 11月, 2010 1 次提交
  30. 09 9月, 2010 1 次提交
  31. 25 8月, 2010 1 次提交
    • T
      6978355: renaming for 6961697 · ffaef974
      twisti 提交于
      Summary: This is the renaming part of 6961697 to keep the actual changes small for review.
      Reviewed-by: kvn, never
      ffaef974
  32. 21 8月, 2010 1 次提交
  33. 16 6月, 2010 1 次提交
  34. 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
  35. 28 5月, 2010 1 次提交
  36. 27 4月, 2010 1 次提交
  37. 09 2月, 2010 1 次提交
  38. 02 2月, 2010 1 次提交
  39. 14 1月, 2010 1 次提交
    • Y
      6896647: card marks can be deferred too long · 651edb8d
      ysr 提交于
      Summary: Deferred card marks are now flushed during the gc prologue. Parallel[Scavege,OldGC] and SerialGC no longer defer card marks generated by COMPILER2 as a result of ReduceInitialCardMarks. For these cases, introduced a diagnostic option to defer the card marks, only for the purposes of testing and diagnostics. CMS and G1 continue to defer card marks. Potential performance concern related to single-threaded flushing of deferred card marks in the gc prologue will be addressed in the future.
      Reviewed-by: never, johnc
      651edb8d
  40. 05 1月, 2010 1 次提交