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
Copy file name to clipboardExpand all lines: README.md
+14-14Lines changed: 14 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -113,17 +113,17 @@ $ sh configure --disable-warnings-as-errors --with-debug-level=$DEBUG_LEVEL
113
113
Then build OpenJDK (this will build MMTk as well):
114
114
115
115
```console
116
-
$ make CONF=linux-x86_64-normal-server-release THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk images
116
+
$ make CONF=linux-x86_64-server-release THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk images
117
117
```
118
118
119
-
The output jdk is then found at `./build/linux-x86_64-normal-server-release/images/jdk`.
119
+
The output jdk is then found at `./build/linux-x86_64-server-release/images/jdk`.
120
120
121
121
> **Note:** The above `make` command will build the `images` target, which is a proper release build of OpenJDK. It is **essential** that you use this target if you are planning on evaluating your build (e.g. measuring performance, gathering minimum heap values, etc). However, if you are simply developing and building incremental changes often, you may want to use the [`default` target or "exploded image"](https://github.com/openjdk/jdk11u/blob/master/doc/building.md#Running-make), which has a marginally shorter build time. However, be wary, as the exploded image is the (roughly) minimal set of outputs required to run the built JDK and is not guaranteed to run all benchmarks. It may have bloated minimum heap values as well.
122
122
>
123
-
> The exploded image can be built as follows. The output jdk can be found at `./build/linux-x86_64-normal-server-$DEBUG_LEVEL/jdk`.
123
+
> The exploded image can be built as follows. The output jdk can be found at `./build/linux-x86_64-server-$DEBUG_LEVEL/jdk`.
124
124
>
125
125
> ```console
126
-
> $ make CONF=linux-x86_64-normal-server-$DEBUG_LEVEL THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk
126
+
> $ make CONF=linux-x86_64-server-$DEBUG_LEVEL THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk
127
127
> ```
128
128
>
129
129
> Again: **do not use the exploded image for performance analysis**.
@@ -151,7 +151,7 @@ stress factor of 4 MB in order to trigger more GC events.
151
151
First we compile MMTk with profiling support:
152
152
153
153
```console
154
-
$ RUSTFLAGS="-Cprofile-generate=/tmp/$USER/pgo-data" make CONF=linux-x86_64-normal-server-release THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk images
154
+
$ RUSTFLAGS="-Cprofile-generate=/tmp/$USER/pgo-data" make CONF=linux-x86_64-server-release THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk images
155
155
$ rm -rf /tmp/$USER/pgo-data/*
156
156
```
157
157
We clear the `/tmp/$USER/pgo-data` directory as during compilation, the JVM we
@@ -162,7 +162,7 @@ We then run `fop` in order to get some profiling data. Note that your location
# JDK is at `build/linux-x86_64-normal-server-release/jdk`
51
+
CONF=linux-x86_64-server-release make
52
+
# JDK is at `build/linux-x86_64-server-release/jdk`
53
53
```
54
54
55
55
## Testing
56
56
57
-
1.`java` binary is at `build/linux-x86_64-normal-server-<DEBUG_LEVEL>/jdk/bin/java`.
57
+
1.`java` binary is at `build/linux-x86_64-server-<DEBUG_LEVEL>/jdk/bin/java`.
58
58
2. Set env `LD_LIBRARY_PATH` to include `$PWD/mmtk/vmbindings/openjdk/target/debug` (or `$PWD/mmtk/vmbindings/openjdk/target/release` if openjdk is built with debug level `release`).
59
59
3. To enable MMTk, pass `-XX:+UseMMTk -XX:-UseCompressedOops` to `java`.
60
60
@@ -63,13 +63,13 @@ e.g.:
63
63
* If `DEBUG_LEVEL` = `fastdebug`, `slowdebug` or `optimized`:
0 commit comments