8281522: Rename ADLC classes which have the same name as hotspot variants

[tstuefe]

I'd like to bring this into JDK17. Its a purely mechanical renaming of classes in ADLC. It does not apply cleanly, but the only conflicts were copyright headers (ADLC gets touched very rarely).

The reason I want this downported is to make future code changes easier and to simplify development. I was on the fence about this one, but since its really low risk, I think it makes sense to downport this.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8281522: Rename ADLC classes which have the same name as hotspot variants

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer) ⚠️ Review applies to e18b494

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/332/head:pull/332
$ git checkout pull/332

Update a local copy of the PR:
$ git checkout pull/332
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/332/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 332

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/332.diff

[bridgekeeper]

👋 Welcome back stuefe! 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 backport pull request has now been updated with issue from the original commit.

[TheRealMDoerr]

I think this makes sense. It's always good to be able to distinguish the ADLC stuff from the rest.

[openjdk]

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

8281522: Rename ADLC classes which have the same name as hotspot variants

Reviewed-by: mdoerr

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.

[tstuefe]

I think this makes sense. It's always good to be able to distinguish the ADLC stuff from the rest.

Thanks Martin!

[tstuefe]

/clean

[openjdk]

@tstuefe This backport pull request is now marked as clean

[TheRealMDoerr]

Note that this PR is still draft!

[mlbridge]

Webrevs

• 00: Full (9e7e1636)

[tstuefe]

/integrate

[openjdk]

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

• ba4e609: 8282382: Report glibc malloc tunables in error reports

Your commit was automatically rebased without conflicts.

[openjdk]

@tstuefe Pushed as commit 83dba03.

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