You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>The regular builds by SAP is using AIX version 7.1, but AIX 5.3 is also supported. See the <ahref="http://cr.openjdk.java.net/~simonis/ppc-aix-port">OpenJDK PowerPC Port Status Page</a> for details.</p>
240
+
<p>Please consult the AIX section of the <ahref="https://wiki.openjdk.java.net/display/Build/Supported+Build+Platforms">Supported Build Platforms</a>OpenJDK Build Wiki page for details about which versions of AIX are supported.</p>
<p>Large portions of the JDK consists of native code, that needs to be compiled to be able to run on the target platform. In theory, toolchain and operating system should be independent factors, but in practice there's more or less a one-to-one correlation between target operating system and toolchain.</p>
<p>If you have multiple versions of Visual Studio installed, <code>configure</code> will by default pick the latest. You can request a specific version to be used by setting <code>--with-toolchain-version</code>, e.g. <code>--with-toolchain-version=2015</code>.</p>
374
374
<p>If you get <code>LINK: fatal error LNK1123: failure during conversion to COFF: file invalid</code> when building using Visual Studio 2010, you have encountered <ahref="http://support.microsoft.com/kb/2757355">KB2757355</a>, a bug triggered by a specific installation order. However, the solution suggested by the KB article does not always resolve the problem. See <ahref="https://stackoverflow.com/questions/10888391">this stackoverflow discussion</a> for other suggestions.</p>
375
375
<h3id="ibm-xl-cc">IBM XL C/C++</h3>
376
-
<p>The regular builds by SAP is using version 12.1, described as <code>IBM XL C/C++ for AIX, V12.1 (5765-J02, 5725-C72) Version: 12.01.0000.0017</code>.</p>
377
-
<p>See the <ahref="http://cr.openjdk.java.net/~simonis/ppc-aix-port">OpenJDK PowerPC Port Status Page</a> for details.</p>
376
+
<p>Please consult the AIX section of the <ahref="https://wiki.openjdk.java.net/display/Build/Supported+Build+Platforms">Supported Build Platforms</a> OpenJDK Build Wiki page for details about which versions of XLC are supported.</p>
<p>Paradoxically, building the JDK requires a pre-existing JDK. This is called the "boot JDK". The boot JDK does not, however, have to be a JDK built directly from the source code available in the OpenJDK Community. If you are porting the JDK to a new platform, chances are that there already exists another JDK for that platform that is usable as boot JDK.</p>
380
379
<p>The rule of thumb is that the boot JDK for building JDK major version <em>N</em> should be a JDK of major version <em>N-1</em>, so for building JDK 9 a JDK 8 would be suitable as boot JDK. However, the JDK should be able to "build itself", so an up-to-date build of the current JDK source is an acceptable alternative. If you are following the <em>N-1</em> rule, make sure you've got the latest update version, since JDK 8 GA might not be able to build JDK 9 on all platforms.</p>
@@ -102,11 +98,29 @@ <h2 id="test-suite-control">Test suite control</h2>
102
98
<p>To separate multiple keyword=value pairs, use <code>;</code> (semicolon). Since the shell normally eats <code>;</code>, the recommended usage is to write the assignment inside qoutes, e.g. <code>JTREG="...;..."</code>. This will also make sure spaces are preserved, as in <code>JTREG="VM_OPTIONS=-XshowSettings -Xlog:gc+ref=debug"</code>.</p>
103
99
<p>(Other ways are possible, e.g. using backslash: <code>JTREG=JOBS=1\;TIMEOUT=8</code>. Also, as a special technique, the string <code>%20</code> will be replaced with space for certain options, e.g. <code>JTREG=VM_OPTIONS=-XshowSettings%20-Xlog:gc+ref=debug</code>. This can be useful if you have layers of scripts and have trouble getting proper quoting of command line arguments through.)</p>
104
100
<p>As far as possible, the names of the keywords have been standardized between test suites.</p>
<p>Some keywords are valid across different test suites. If you want to run tests from multiple test suites, or just don't want to care which test suite specific control variable to use, then you can use the general TEST_OPTS control variable.</p>
103
+
<p>There are also some keywords that applies globally to the test runner system, not to any specific test suites. These are also available as TEST_OPTS keywords.</p>
106
104
<h4id="jobs">JOBS</h4>
105
+
<p>Currently only applies to JTReg.</p>
106
+
<h4id="timeout_factor">TIMEOUT_FACTOR</h4>
107
+
<p>Currently only applies to JTReg.</p>
108
+
<h4id="vm_options">VM_OPTIONS</h4>
109
+
<p>Applies to JTReg, GTest and Micro.</p>
110
+
<h4id="java_options">JAVA_OPTIONS</h4>
111
+
<p>Applies to JTReg, GTest and Micro.</p>
112
+
<h4id="aot_modules">AOT_MODULES</h4>
113
+
<p>Applies to JTReg and GTest.</p>
114
+
<h4id="jcov">JCOV</h4>
115
+
<p>This keywords applies globally to the test runner system. If set to <code>true</code>, it enables JCov coverage reporting for all tests run. To be useful, the JDK under test must be run with a JDK built with JCov instrumentation (<code>configure --with-jcov=<path to directory containing lib/jcov.jar></code>, <code>make jcov-image</code>).</p>
116
+
<p>The simplest way to run tests with JCov coverage report is to use the special target <code>jcov-test</code> instead of <code>test</code>, e.g. <code>make jcov-test TEST=jdk_lang</code>. This will make sure the JCov image is built, and that JCov reporting is enabled.</p>
117
+
<p>The JCov report is stored in <code>build/$BUILD/test-results/jcov-output</code>.</p>
118
+
<p>Please note that running with JCov reporting can be very memory intensive.</p>
119
+
<h3id="jtreg-keywords">JTReg keywords</h3>
120
+
<h4id="jobs-1">JOBS</h4>
107
121
<p>The test concurrency (<code>-concurrency</code>).</p>
108
-
<p>Defaults to TEST_JOBS (if set by <code>--with-test-jobs=</code>), otherwise it defaults to JOBS, except for Hotspot, where the default is <em>number of CPU cores/2</em>, but never more than 12.</p>
109
-
<h4id="timeout">TIMEOUT</h4>
122
+
<p>Defaults to TEST_JOBS (if set by <code>--with-test-jobs=</code>), otherwise it defaults to JOBS, except for Hotspot, where the default is <em>number of CPU cores/2</em> (for sparc, if more than 16 cpus, then <em>number of CPU cores/5</em>, otherwise <em>number of CPU cores/4</em>), but never more than <em>memory size in GB/2</em>.</p>
<p>Limit memory consumption (<code>-Xmx</code> and <code>-vmoption:-Xmx</code>, or none).</p>
126
140
<p>Limit memory consumption for JTReg test framework and VM under test. Set to 0 to disable the limits.</p>
127
141
<p>Defaults to 512m, except for hotspot, where it defaults to 0 (no limit).</p>
142
+
<h4id="keywords">KEYWORDS</h4>
143
+
<p>JTReg kewords sent to JTReg using <code>-k</code>. Please be careful in making sure that spaces and special characters (like <code>!</code>) are properly quoted. To avoid some issues, the special value <code>%20</code> can be used instead of space.</p>
<p>Use additional problem lists file or files, in addition to the default ProblemList.txt located at the JTReg test roots.</p>
146
+
<p>If multiple file names are specified, they should be separated by space (or, to help avoid quoting issues, the special value <code>%20</code>).</p>
147
+
<p>The file names should be either absolute, or relative to the JTReg test root of the tests to be run.</p>
128
148
<h4id="options">OPTIONS</h4>
129
149
<p>Additional options to the JTReg test framework.</p>
130
150
<p>Use <code>JTREG="OPTIONS=--help all"</code> to see all available JTReg options.</p>
131
-
<h4id="java_options">JAVA_OPTIONS</h4>
151
+
<h4id="java_options-1">JAVA_OPTIONS</h4>
132
152
<p>Additional Java options to JTReg (<code>-javaoption</code>).</p>
133
-
<h4id="vm_options">VM_OPTIONS</h4>
153
+
<h4id="vm_options-1">VM_OPTIONS</h4>
134
154
<p>Additional VM options to JTReg (<code>-vmoption</code>).</p>
155
+
<h4id="aot_modules-1">AOT_MODULES</h4>
156
+
<p>Generate AOT modules before testing for the specified module, or set of modules. If multiple modules are specified, they should be separated by space (or, to help avoid quoting issues, the special value <code>%20</code>).</p>
135
157
<h3id="gtest-keywords">Gtest keywords</h3>
136
158
<h4id="repeat">REPEAT</h4>
137
159
<p>The number of times to repeat the tests (<code>--gtest_repeat</code>).</p>
138
160
<p>Default is 1. Set to -1 to repeat indefinitely. This can be especially useful combined with <code>OPTIONS=--gtest_break_on_failure</code> to reproduce an intermittent problem.</p>
139
161
<h4id="options-1">OPTIONS</h4>
140
162
<p>Additional options to the Gtest test framework.</p>
141
163
<p>Use <code>GTEST="OPTIONS=--help"</code> to see all available Gtest options.</p>
164
+
<h4id="aot_modules-2">AOT_MODULES</h4>
165
+
<p>Generate AOT modules before testing for the specified module, or set of modules. If multiple modules are specified, they should be separated by space (or, to help avoid quoting issues, the special value <code>%20</code>).</p>
<p>Amount of time to spend in each warmup iteration. Same as specifying <code>-w <num></code>.</p>
153
177
<h4id="results_format">RESULTS_FORMAT</h4>
154
178
<p>Specify to have the test run save a log of the values. Accepts the same values as <code>-rff</code>, i.e., <code>text</code>, <code>csv</code>, <code>scsv</code>, <code>json</code>, or <code>latex</code>.</p>
155
-
<h4id="vm_options-1">VM_OPTIONS</h4>
179
+
<h4id="vm_options-2">VM_OPTIONS</h4>
156
180
<p>Additional VM arguments to provide to forked off VMs. Same as <code>-jvmArgs <args></code></p>
0 commit comments