8366660: Sort share/nmt includes

[fandreuz]

Sort include statements in hotspot/share/nmt using SortIncludes.java. I'm also removing a couple unnecessary includes.

Passes tier1.

---

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-8366660: Sort share/nmt includes (Enhancement - P4)

Reviewers

• Albert Mingkun Yang (@albertnetymk - Reviewer)
• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27042

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8366660: Sort share/nmt includes

Reviewed-by: ayang, shade

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 5 new commits pushed to the master branch:

• 1feb9bd: 8365557: Parallel: Refactor ParallelScavengeHeap::mem_allocate_work
• eea50fb: 8356439: Rename JavaLangAccess::*NoRepl methods
• 3184714: 8325766: Extend CertificateBuilder to create trust and end entity certificates programmatically
• ... and 2 more: https://git.openjdk.org/jdk/compare/523bc77981cfe82956d2176f74917c41788da6db...master

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@albertnetymk, @shipilev) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

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

• hotspot-runtime

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 (ab22f2c2)

[shipilev]

Looks fine, thanks.

[fandreuz]

/integrate

[openjdk]

@fandreuz
Your change (at version ab22f2c) is now ready to be sponsored by a Committer.

[shipilev]

Yeah, wait 24 hours. This is borderline trivial, but there is no need to rush.

[shipilev]

/sponsor

[openjdk]

Going to push as commit 7c70e73.
Since your change was applied there have been 18 commits pushed to the master branch:

• 8c4090c: 8329077: C2 SuperWord: Add MoveD2L, MoveL2D, MoveF2I, MoveI2F
• e268563: 8366476: Test gc/z/TestSmallHeap.java fails OOM with many NUMA nodes
• 5052a7e: 8246037: Shenandoah: update man pages to mention -XX:+UseShenandoahGC
• ... and 15 more: https://git.openjdk.org/jdk/compare/523bc77981cfe82956d2176f74917c41788da6db...master

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @fandreuz Pushed as commit 7c70e73.

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