8331432: Clean up comments in GenArguments::initialize_size_info()

[xiaotaonan]

Clean up comments in GenArguments::initialize_size_info()

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8331432: Clean up comments in GenArguments::initialize_size_info() (Enhancement - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19223/head:pull/19223
$ git checkout pull/19223

Update a local copy of the PR:
$ git checkout pull/19223
$ git pull https://git.openjdk.org/jdk.git pull/19223/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 19223

View PR using the GUI difftool:
$ git pr show -t 19223

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19223.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back xiaotaonan! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@xiaotaonan The following label will be automatically applied to this pull request:

• hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (b835e37f)

[xiaotaonan]

@lgxbslgx

[lgxbslgx]

The issue states there are two places which need to be revised. So the warning message is good to be adjusted in this PR.

[kimbarrett]

JDK-8331432 also mentions this warning message as needing cleanup.
It should be similar to the one below about initial vs min old size, rather than incorrectly mentioning
max heap size and printing MaxHeapSize.
Except it would be useful if both includes both the initial and bound values.
Also, prefer "%zu" rather than SIZE_FORMAT when updating the messages.