Merge pull request #16546 from Sreekala-Gopakumar/36ReleaseNoteDraft

Updated 0.36.0 release notes

doc/release-notes/0.36/0.36.md

@@ -1,5 +1,5 @@
 <!--
-* Copyright (c) 2022, 2022 IBM Corp. and others
+* Copyright (c) 2023 IBM Corp. and others
 *
 * This program and the accompanying materials are made
 * available under the terms of the Eclipse Public License 2.0
@@ -48,18 +48,46 @@ The following table covers notable changes in v0.36.0. Further information about
 </thead>
 <tbody>
 
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16256">#16256</a></td>
+<td valign="top">The location of the default directory for the shared cache and snapshot is changed to the <tt>.cache/javasharedresources</tt> in the user's home directory.</td>
+<td valign="top">All versions (AIX&reg;, Linux&reg;, macOS&reg;)</td>
+<td valign="top">This change is for non-Windows&trade; and non-z/OS&reg; platforms and applies only if <tt>-Xshareclasses:groupAccess</tt> is not used. If <tt>groupAccess</tt> is used, the directory that gets set remains as <tt>/tmp/javasharedresources/</tt>.</td>
+</tr>
+
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16133">#16133</a></td>
+<td valign="top">New <tt>-XX:[+|-]MergeCompilerOptions</tt> option is added to enable or disable the merging of multiple -Xjit or -Xaot options into a single -Xjit or -Xaot option.</td>
+<td valign="top">All versions</td>
+<td valign="top"> By default, if you specify <tt>-Xjit</tt> option (or <tt>-Xaot</tt> option) multiple times, only the last option takes effect. Therefore, on adding an <tt>-Xjit</tt> option, the resultant behavior might not be as expected, if any instance of this option already exists. You can use the <tt>-XX:+MergeCompilerOptions</tt> option to merge all the existing instances of the <tt>-Xjit</tt> options logically.</td>
+</tr>
+
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16166">#16166</a></td>
+<td valign="top">Default JITServer AOT cache is named as <tt>default</tt>.</td>
+<td valign="top">All versions (Linux)</td>
+<td valign="top">A JITServer instance can have several AOT caches, each with its own name and containing different versions of compiled methods. Client JVMs with different profiles of execution can connect to the same JITServer instance, but access the cache with compiled methods optimized for their own profile with the <tt>-XX:JITServerAOTCacheName</tt> option. Earlier, if the cache name was not specified in this option, the default was to use a nameless cache. The default AOT cache name is now changed to <tt>default</tt>.</td>
+</tr>
+
 <tr>
 <td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/15775">#15775</a></td>
-<td valign="top">New <tt>-XX:JITServerAOTmx</tt> option added for specifying the maximum amount of memory that can be used by the JITServer AOT cache</td>
-<td valign="top">All versions (Linux&reg;)</td>
+<td valign="top">New <tt>-XX:JITServerAOTmx</tt> option is added for specifying the maximum amount of memory that can be used by the JITServer AOT cache.</td>
+<td valign="top">All versions (Linux)</td>
 <td valign="top">The maximum amount of memory that all the AOT cache instances combined can use at the server is 300 MB, by default. You can change this value by using the <tt>-XX:JITServerAOTmx=&ltsize&gt</tt> option. When the cache size reaches the specified limit, new clients cannot create new AOT cache instances or add new compiled methods to the existing AOT cache instances.</td>
 </tr>
 
 <tr>
-<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16256">#16256</a></td>
-<td valign="top">The location of the default directory for the shared cache and snapshot is changed to the <tt>.cache/javasharedresources</tt> in the user's home directory</td>
-<td valign="top">All versions (AIX&reg;, Linux, macOS&reg;)</td>
-<td valign="top">This change is for non-Windows&trade; and non-z/OS&reg; platforms and applies only if <tt>-Xshareclasses:groupAccess</tt> is not used. If <tt>groupAccess</tt> is used, the directory that gets set remains as <tt>/tmp/javasharedresources/</tt>.</td>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16075">#16075</a></td>
+<td valign="top">New <tt>-XX:[+|-]JITServerAOTCachePersistence</tt> option is added to specify whether the JITServer server periodically saves its AOT caches to files.</td>
+<td valign="top">All versions (Linux)</td>
+<td valign="top">With the <tt>-XX:+JITServerAOTCachePersistence</tt> option, the JITServer server periodically saves its AOT caches to files. Other JITServer instances can then load these caches the first time that a client requests a particular cache. This feature is useful to improve performance, especially in scenarios where JITServer instances are started up and shut down regularly.</td>
+</tr>
+
+<tr>
+<td valign="top"><a href="https://github.com/eclipse-openj9/openj9/issues/16075">#16075</a></td>
+<td valign="top">New <tt>-XX:JITServerAOTCacheDir</tt> option is added to specify the directory to be used for saving and loading JITServer AOT cache files.</td>
+<td valign="top">All versions (Linux)</td>
+<td valign="top">If the JITServer AOT cache persistence feature is enabled (<tt>-XX:+JITServerAOTCachePersistence</tt>) and the client JVM asks for an AOT cache that is not already present in server's memory, the server attempts to load the named AOT cache from file. You can use the <tt>-XX:JITServerAOTCacheDir=&ltdirectory&gt</tt> option to specify the directory where the AOT cache must be saved to or loaded from.</td>
 </tr>
 
 </tbody>
@@ -108,6 +136,14 @@ on x64 platforms, but builds with OpenJDK 17 and later also require more stack s
 <td valign="top">Avoid using the <tt>-XX:+ShowHiddenFrames</tt> option with OpenJDK 18 and later.</td>
 </tr>
 
+<tr>
+<td valign="top">-</td>
+<td valign="top">Support for OpenJDK 19 is not yet available due to outstanding issues, as listed in the <a href="https://github.com/eclipse-openj9/openj9/milestone/35">milestone 35</a> plan.</td>
+<td valign="top">All platforms</td>
+<td valign="top">OpenJDK 19 support will be added in a future OpenJ9 release if possible before the release of OpenJDK 20 in March. This work might delay support for OpenJDK 20 (you can follow the progress of OpenJDK 20 support in the <a href="https://github.com/eclipse-openj9/openj9/milestone/40">milestone 40</a> plan). The information in the <a href=https://www.eclipse.org/openj9/docs/openj9_support/#eclipse-openj9-releases>Eclipse OpenJ9 releases table</a> in the documentation is therefore more likely to change than usual.</td>
+<td valign="top">None</td>
+</tr>
+
 </tbody>
 </table>