1. 23 11月, 2013 1 次提交
  2. 22 11月, 2013 1 次提交
  3. 18 11月, 2013 1 次提交
  4. 14 11月, 2013 1 次提交
  5. 13 11月, 2013 1 次提交
  6. 01 11月, 2013 1 次提交
    • C
      8026946: JvmtiEnv::SetBreakpoint and JvmtiEnv::ClearBreakpoint should use MethodHandle · b1ca3bae
      coleenp 提交于
      8026948: JvmtiEnv::SetBreakpoint and JvmtiEnv::ClearBreakpoint might not work with anonymous classes
      Summary: Walk methods in breakpoints for marking on stack so they aren't deallocated by redefine classes.  Use class_holder rather than class_loader to keep GC from reclaiming class owning the method.
      Reviewed-by: sspitsyn, ehelin, sla
      b1ca3bae
  7. 31 10月, 2013 1 次提交
  8. 24 10月, 2013 2 次提交
  9. 20 10月, 2013 1 次提交
  10. 18 10月, 2013 2 次提交
  11. 24 10月, 2013 1 次提交
  12. 09 10月, 2013 1 次提交
  13. 08 10月, 2013 2 次提交
  14. 09 10月, 2013 1 次提交
    • T
      8003420: NPG: make new GC root for pd_set · e540de76
      tschatzl 提交于
      Summary: Move protection domain oops from system dictionary entries into a seperate set; the system dictionary references entries in that set now. This allows fast iteration during non-classunloading garbage collection. Implementation based on initial prototype from Ioi Lam (iklam).
      Reviewed-by: coleenp, iklam
      e540de76
  15. 07 10月, 2013 1 次提交
  16. 04 10月, 2013 1 次提交
  17. 02 10月, 2013 1 次提交
  18. 01 10月, 2013 1 次提交
  19. 29 9月, 2013 1 次提交
  20. 27 9月, 2013 1 次提交
  21. 26 9月, 2013 1 次提交
    • H
      7195622: CheckUnhandledOops has limited usefulness now · 087226b2
      hseigel 提交于
      Summary: Enable CHECK_UNHANDLED_OOPS in fastdebug builds across all supported platforms.
      Reviewed-by: coleenp, hseigel, dholmes, stefank, twisti, ihse, rdurbin
      Contributed-by: lois.foltan@oracle.com
      087226b2
  22. 20 9月, 2013 1 次提交
    • S
      8024974: Incorrect use of GC_locker::is_active() · 427aeb32
      stefank 提交于
      Summary: SymbolTable and StringTable can make calls to GC_locker::is_active() outside a safepoint. This isn't safe because the GC_locker active state (lock count) is only updated at a safepoint and only remains valid as long as _needs_gc is true. However, outside a safepoint_needs_gc can change to false at any time, which makes it impossible to do a correct call to is_active() in that context. In this case these calls can just be removed since the input argument to basic_add() should never be on the heap and so there's no need to check the GC_locker state. This change also adjusts the assert() in is_active() to makes sure all calls to this function are always done under a safepoint.
      Reviewed-by: brutisso, dcubed
      Contributed-by: per.liden@oracle.com
      427aeb32
  23. 18 9月, 2013 1 次提交
  24. 17 9月, 2013 1 次提交
  25. 14 9月, 2013 1 次提交
  26. 13 9月, 2013 1 次提交
  27. 11 9月, 2013 1 次提交
  28. 10 9月, 2013 1 次提交
  29. 31 8月, 2013 1 次提交
  30. 29 8月, 2013 1 次提交
  31. 28 8月, 2013 1 次提交
  32. 27 8月, 2013 1 次提交
  33. 26 8月, 2013 1 次提交
  34. 24 8月, 2013 1 次提交
  35. 20 8月, 2013 1 次提交
  36. 07 8月, 2013 1 次提交
  37. 03 8月, 2013 1 次提交