8390778: [PPC] : stubgen stubs using incorrect StubCodeMark constructor

[varada1110]

Hi all,

This pull request contains a backport of commit 4a02985e from the openjdk/jdk repository.

The commit being backported was authored by Varada M on 2 Sep 2026 and was reviewed by Andrew Dinn and Amit Kumar.

Thanks!

---

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

---

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
• JDK-8390778 needs maintainer approval

Issue

• JDK-8390778: [PPC] : stubgen stubs using incorrect StubCodeMark constructor (Bug - P4)

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk25u-dev.git pull/786/head:pull/786
$ git checkout pull/786

Update a local copy of the PR:
$ git checkout pull/786
$ git pull https://git.openjdk.org/jdk25u-dev.git pull/786/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 786

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk25u-dev/pull/786.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (a6375bc4)

[TheRealMDoerr]

Backport looks correct. Please explain why it isn't clean for future backports. I figured it out this time. Not sure if this is important enough for a backport, but ok.

[openjdk]

⚠️ @varada1110 This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.