1. 21 2月, 2014 1 次提交
  2. 23 4月, 2014 1 次提交
  3. 11 11月, 2013 1 次提交
  4. 10 11月, 2013 1 次提交
  5. 02 11月, 2013 1 次提交
  6. 22 10月, 2013 3 次提交
  7. 07 10月, 2013 1 次提交
  8. 05 10月, 2013 1 次提交
  9. 04 10月, 2013 1 次提交
  10. 03 10月, 2013 1 次提交
  11. 01 10月, 2013 1 次提交
  12. 14 9月, 2013 1 次提交
  13. 11 9月, 2013 1 次提交
    • T
      8010722: assert: failed: heap size is too big for compressed oops · 95a96a89
      tschatzl 提交于
      Summary: Use conservative assumptions of required alignment for the various garbage collector components into account when determining the maximum heap size that supports compressed oops. Using this conservative value avoids several circular dependencies in the calculation.
      Reviewed-by: stefank, dholmes
      95a96a89
  14. 16 8月, 2013 1 次提交
    • S
      8007074: SIGSEGV at ParMarkBitMap::verify_clear() · e52f7476
      stefank 提交于
      Summary: Replace the broken large pages implementation on Linux. New flag: -XX:+UseTransparentHugePages - Linux specific flag to turn on transparent huge page hinting with madvise(..., MAP_HUGETLB). Changed behavior: -XX:+UseLargePages - tries to use -XX:+UseTransparentHugePages before trying other large pages implementations (on Linux). Changed behavior: -XX:+UseHugeTLBFS - Use upfront allocation of Large Pages instead of using the broken implementation to dynamically committing large pages. Changed behavior: -XX:LargePageSizeInBytes - Turned off the ability to use this flag on Linux and provides warning to user if set to a value different than the OS chosen large page size. Changed behavior: Setting no large page size - Now defaults to use -XX:UseTransparentHugePages if the OS supports it. Previously, -XX:+UseHugeTLBFS was chosen if the OS was configured to use large pages.
      Reviewed-by: tschatzl, dcubed, brutisso
      e52f7476
  15. 15 5月, 2013 2 次提交
    • T
      6843347: Boundary values in some public GC options cause crashes · f0036e39
      tschatzl 提交于
      Summary: Setting some public integer options to specific values causes crashes or undefined GC behavior. This patchset adds the necessary argument checking for these options.
      Reviewed-by: jmasa, brutisso
      f0036e39
    • M
      8012902: remove use of global operator new - take 2 · 73092391
      minqi 提交于
      Summary: The fix of 8010992, disable use of global operator new and new[] which caused failure on some tests. This takes two of the bugs also add ALLOW_OPERATOR_NEW_USAGE to prevent crash for third party code calling operator new of jvm on certain platforms.
      Reviewed-by: coleenp, dholmes, zgu
      Contributed-by: yumin.qi@oracle.com
      73092391
  16. 13 5月, 2013 1 次提交
    • T
      8014058: Regression tests for 8006088 · ba0f7cb3
      tschatzl 提交于
      Summary: The patch for 8006088 misses regression tests after a merge error, this CR provides them.
      Reviewed-by: jwilhelm, tamao, jmasa
      ba0f7cb3
  17. 06 5月, 2013 2 次提交
  18. 22 4月, 2013 1 次提交
  19. 20 4月, 2013 1 次提交
  20. 28 3月, 2013 1 次提交
  21. 13 3月, 2013 1 次提交
  22. 15 2月, 2013 1 次提交
  23. 28 1月, 2013 1 次提交
  24. 24 1月, 2013 1 次提交
  25. 30 12月, 2012 1 次提交
  26. 04 12月, 2012 1 次提交
  27. 27 11月, 2012 1 次提交
  28. 31 10月, 2012 1 次提交
  29. 19 9月, 2012 1 次提交
  30. 02 9月, 2012 1 次提交
  31. 26 9月, 2011 1 次提交
  32. 17 6月, 2011 1 次提交
  33. 29 4月, 2011 1 次提交
  34. 17 3月, 2011 1 次提交
    • Y
      6896099: Integrate CMS heap ergo with default heap sizing ergo · 394e03cc
      ysr 提交于
      6627787: CMS: JVM refuses to start up with -Xms16m -Xmx16m
      7000125: CMS: Anti-monotone young gen sizing with respect to maximum whole heap size specification
      7027529: CMS: retire CMSUseOldDefaults flag
      Summary: Simplify CMS heap sizing code, relying on ergonomic initial sizing consistent with other collectors for the most part, controlling only young gen sizing to rein in pause times. Make CMS young gen sizing default statically cpu-dependant. Remove inconsistencies wrt generation sizing and policy code, allowing for the fixing for 6627787 and 7000125. For 7027529, retire the flag CMSUseOldDefaults which had been introduced as a bridge from JDK 5 to JDK 6 a number of years ago.
      Reviewed-by: brutisso, poonam
      394e03cc
  35. 08 12月, 2010 1 次提交
    • Y
      7001033: assert(gch->gc_cause() == GCCause::_scavenge_alot ||... · 8be7836d
      ysr 提交于
      7001033: assert(gch->gc_cause() == GCCause::_scavenge_alot || !gch->incremental_collection_failed())
      7002546: regression on SpecJbb2005 on 7b118 comparing to 7b117 on small heaps
      Summary: Relaxed assertion checking related to incremental_collection_failed flag to allow for ExplicitGCInvokesConcurrent behaviour where we do not want a failing scavenge to bail to a stop-world collection. Parameterized incremental_collection_will_fail() so we can selectively use, or not use, as appropriate, the statistical prediction at specific use sites. This essentially reverts the scavenge bail-out logic to what it was prior to some recent changes that had inadvertently started using the statistical prediction which can be noisy in the presence of bursty loads. Added some associated verbose non-product debugging messages.
      Reviewed-by: johnc, tonyp
      8be7836d
  36. 24 11月, 2010 1 次提交