8348515: Add docs for -XX:AOT* options in java man pages#23287
8348515: Add docs for -XX:AOT* options in java man pages#23287iklam wants to merge 5 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back iklam! A progress list of the required criteria for merging this PR into |
|
@iklam This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 37 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
|
@iklam To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command. Applicable Labels
|
|
/label hotspot-runtime |
|
@iklam |
Webrevs
|
vnkozlov
left a comment
There was a problem hiding this comment.
I am not sure if there is rule about ordering flags description alphabetically.
I would exactly reverse the order you have to put more important flags first.
| - A particular application (as expressed by `-classpath`, `-jar`, or `--module-path`.) | ||
| - A particular JDK release. | ||
| - A particular OS and CPU architecture. |
There was a problem hiding this comment.
What about VM's flags/settings (GCs for example)?
There was a problem hiding this comment.
The impact of flags is duscissed in the "loading of an AOTCache can fail for a number of reasons" section below. Also, I chose not to enumerate all the possible flag incompatibilities, as there's a pretty exhaustive list in JEP 483.
I changed the order of flags to be: AOTCache -> AOTConfiguration -> AOTMode -> AOTClassLinking. |
src/java.base/share/man/java.md
Outdated
|
|
||
| - **Assembly:** We use the AOT Configuration file to produce an AOTCache. | ||
|
|
||
| - **Production:** We execut the application with the AOTCache for better |
There was a problem hiding this comment.
typo: 'We execut' --> 'We execute'
vnkozlov
left a comment
There was a problem hiding this comment.
Good, except Andrew's comment.
adinn
left a comment
There was a problem hiding this comment.
Yes, all good and reads well.
|
Going to push as commit 46f48e4.
Your commit was automatically rebased without conflicts. |
|
The command line flag For comparison, take any other camel-case flag like |
|
(Oops, you just pushed; sorry about the late feedback. I still think the change should be made.) |
|
Also, the word "appication" is a typo. And "representitive". And "options" should be "option" in "If this options is specified". |
| The Ahead-of-Time Cache (AOTCache) is a container introduced in JDK 24 for | ||
| storing artifacts produced by AOT optimizations. The AOTCache currently contains | ||
| Java classes and heap objects. The plans is to include other types of artifacts, | ||
| such as execution profiles and compiled methods, in future JDK releases. |
There was a problem hiding this comment.
s/plans/plan/ or reframe the sentence as:
In future JDK releases, the AOT cache may contain additional artifacts, such as execution profiles and compiled methods.
There was a problem hiding this comment.
Sigh -- missed this one too. Sadly, English language grammar requires far more eyes than formal language grammar.
I added docs for the following options added by JEP 483
For a (semi) rendered version, see https://github.com/iklam/jdk/blob/8348515-docs-for-aot-options/src/java.base/share/man/java.md#ahead-of-time-cache
(Some of the rendering by GitHub looks odd, but the java.1 and java.html pages produced by the build should look fine)
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23287/head:pull/23287$ git checkout pull/23287Update a local copy of the PR:
$ git checkout pull/23287$ git pull https://git.openjdk.org/jdk.git pull/23287/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23287View PR using the GUI difftool:
$ git pr show -t 23287Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23287.diff
Using Webrev
Link to Webrev Comment