jdk-24 fork (from: https://github.com/openjdk/jdk) with modifications to be used in Wildcard-Usage analysis tools
Go to file
John Cuthbertson 72c2cfef4f 7096030: G1: PrintGCDetails enhancements
7102445: G1: Unnecessary Resource allocations during RSet scanning

Add a new per-worker thread line in the PrintGCDetails output. GC Worker Other is the difference between the elapsed time for the parallel phase of the evacuation pause and the sum of the times of the sub-phases (external root scanning, mark stack scanning, RSet updating, RSet scanning, object copying, and termination) for that worker. During RSet scanning, stack allocate DirtyCardToOopClosure objects; allocating these in a resource area was causing abnormally high GC Worker Other times while the worker thread freed ResourceArea chunks.

Reviewed-by: tonyp, jwilhelm, brutisso
2011-10-23 23:06:06 -07:00
.jcheck 7048009: Update .jcheck/conf files for JDK 8 2011-05-24 15:28:39 -07:00
corba Added tag jdk8-b09 for changeset 44d496c3c830 2011-10-13 10:35:29 -07:00
hotspot 7096030: G1: PrintGCDetails enhancements 2011-10-23 23:06:06 -07:00
jaxp Added tag jdk8-b09 for changeset 072884311758 2011-10-13 10:35:39 -07:00
jaxws Added tag jdk8-b09 for changeset 8124579f60fd 2011-10-13 10:35:40 -07:00
jdk Merge 2011-10-17 19:06:53 -07:00
langtools Merge 2011-10-17 19:07:26 -07:00
make 7087428: move client tests out of jdk_misc 2011-09-08 09:06:09 +08:00
test Merge 2011-04-12 18:35:57 -07:00
.hgignore 6631003: Add hg tip changeset to build image 2011-04-26 16:30:00 -07:00
.hgtags Added tag jdk8-b09 for changeset fbf3cabc9e3b 2017-07-05 17:52:45 +02:00
.hgtags-top-repo Added tag jdk8-b09 for changeset 56ae1c1e8584 2011-10-13 10:35:24 -07:00
ASSEMBLY_EXCEPTION Initial load 2007-12-01 00:00:00 +00:00
get_source.sh 7003845: README-builds document proper location of forest extension, provide alternatives 2010-12-22 12:25:52 -08:00
LICENSE 7013964: openjdk LICENSE file needs rebranding 2011-02-16 13:29:01 -08:00
Makefile 7043700: Regression for IcedTea builds 2011-05-16 08:40:01 -07:00
README 7071275: Fix jdk7 references in README files, remove Forest Extension mentions 2011-07-26 21:54:25 +02:00
README-builds.html 7071275: Fix jdk7 references in README files, remove Forest Extension mentions 2011-07-26 21:54:25 +02:00
THIRD_PARTY_README 7057046: Add embedded license to THIRD PARTY README 2011-06-22 10:09:19 -07:00

README:
  This file should be located at the top of the OpenJDK Mercurial root
  repository. This root repository will include a "make" directory,
  and a Makefile for building the entire OpenJDK.
  A full OpenJDK repository set (forest) should also include the following
  6 nested repositories:
    "jdk", "hotspot", "langtools", "corba", "jaxws"  and "jaxp".
  There are also several source downloads for the jax* repositories that
  will be needed.

  This one root repository can be obtained with something like:

    hg clone http://hg.openjdk.java.net/jdk8/jdk8 openjdk8
  
  To make sure you have all the nested repositories, you can run the
  get_source.sh script located in the same respository as this file:

    cd openjdk8 && sh ./get_source.sh

  People unfamiliar with Mercurial should read the first few chapters of
  the Mercurial book: http://hgbook.red-bean.com/read/

  See http://openjdk.java.net/ for more information about the OpenJDK.

Simple Build Instructions:
  
  0. Get the necessary system software/packages installed on your system, see
     http://hg.openjdk.java.net/jdk8/build/raw-file/tip/README-builds.html

  1. If you don't have a jdk6 installed, download and install a JDK 6 from
     http://java.sun.com/javase/downloads/index.jsp
     Set the environment variable ALT_BOOTDIR to the location of JDK 6.

  2. Check the sanity of doing a build with your current system:
       make sanity
     See README-builds.html if you run into problems.
  
  3. Do a complete build of the OpenJDK:
       make all
     The resulting JDK image should be found in build/*/j2sdk-image

where make is GNU make 3.81 or newer, /usr/bin/make on Linux usually
is 3.81 or newer.

Complete details are available in README-builds.html.