8381829: Obsolete AggressiveHeap

[jsikstro]

Hello,

This PR obsoletes the AggressiveHeap flag after being deprecated in JDK26. All changes are straightforward, and we can now simplify Arguments::limit_heap_by_allocatable_memory to only rely on the currently chosen GC, instead of falling back to a seemingly magic number when AggressiveHeap was defined.

Testing:

• Oracle's tier1-5

---

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

Progress

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

Issue

• JDK-8381829: Obsolete AggressiveHeap (Enhancement - P4)

Reviewers

• David Holmes (@dholmes-ora - Reviewer)
• Albert Mingkun Yang (@albertnetymk - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 30768

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back jsikstro! 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]

@jsikstro 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:

8381829: Obsolete AggressiveHeap

Reviewed-by: dholmes, ayang

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

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

• hotspot

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

• 01: Full - Incremental (c9fd24d4)
• 00: Full (4013638c)

[openjdk]

The total number of required reviews for this PR has been set to 2 based on the presence of this label: hotspot. This can be overridden with the /reviewers command.

[dholmes-ora]

LGTM!

Thanks

[jsikstro]

Thank you for the reviews! @dholmes-ora @albertnetymk
/integrate

[openjdk]

Going to push as commit 7e26bc6.
Since your change was applied there has been 1 commit pushed to the master branch:

• 21b9a50: 8370102: Print method signatures in edge cases when using TraceBytecodes

Your commit was automatically rebased without conflicts.

[openjdk]

@jsikstro Pushed as commit 7e26bc6.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.