8374210: [BACKOUT] Move input validation checks to Java for java.lang.StringCoding intrinsics

[vy]

Back out java.lang.StringCoding changes delivered in JDK-8361842 (#25998 & 655dc51), which causes regressions reported in JDK-8374210.

---

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-8374210: [BACKOUT] Move input validation checks to Java for java.lang.StringCoding intrinsics (Bug - P2)(⚠️ The fixVersion in this issue is [26] but the fixVersion in .jcheck/conf is 27, a new backport will be created when this pr is integrated.)

Reviewers

• Aleksey Shipilev (@shipilev - Reviewer)
• Tobias Hartmann (@TobiHartmann - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 29055

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[vy]

Tier 1-3 are clear on c8acc80.

[bridgekeeper]

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

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

8374210: [BACKOUT] Move input validation checks to Java for java.lang.StringCoding intrinsics

Reviewed-by: shade, thartmann

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

• 532a0a6: 8372950: Pem.pemEncoded should cache the Pattern
• 5df183b: 8373476: (tz) Update Timezone Data to 2025c
• 938bbd5: 8374518: C1: Remove dead LinearScanStatistic::Counter::counter_fpu_stack
• ... and 11 more: https://git.openjdk.org/jdk/compare/e676c9de3da3b820081cde1b11c0df3129787130...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.

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

[openjdk]

@vy The following labels will be automatically applied to this pull request:

• core-libs
• hotspot
• i18n
• nio
• security

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

[mlbridge]

Webrevs

• 00: Full (c8acc80b)

[vy]

Matching the labels with #25998 that this PR is reverting:

/label remove i18n,nio,security

[openjdk]

@vy
The i18n label was successfully removed.

The nio label was successfully removed.

The security label was successfully removed.

[shipilev]

This does not look like a clean backout -- the incoming/outgoing line counts do not match against the original commit -- so extra caution is needed in reviews.

Apart from the inadverent (?) addition in JavaLangAccess.java, there seem to be hunk differences in some sun/nio/cs files; I assume those are intentional?

[vy]

there seem to be hunk differences in some sun/nio/cs files; I assume those are intentional?

Yes, they are clean reverts of the associated files changed in 655dc51.

[TobiHartmann]

Looks good to me.

[vy]

@TobiHartmann, @shipilev, thanks so much for your kind help, and reviews.
As I stated earlier, Tier 1-3 are clear using c8acc80, and I see no other remarks.

/integrate

[openjdk]

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

• a01283a: 8374632: Broken list layout in the man page of jlink
• c1c0ac8: 8342772: Assert in LateInlineMHCallGenerator::do_late_inline_check
• 5c6947f: 8373429: gc/g1/TestCodeCacheUnloadDuringConcCycle fails on various platforms
• ... and 27 more: https://git.openjdk.org/jdk/compare/e676c9de3da3b820081cde1b11c0df3129787130...master

Your commit was automatically rebased without conflicts.

[openjdk]

@vy Pushed as commit 7e18de1.

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

[vy]

/backport :jdk26

[openjdk]

@vy the backport was successfully created on the branch backport-vy-7e18de13-jdk26 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk26, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 7e18de13 from the openjdk/jdk repository.

The commit being backported was authored by Volkan Yazici on 7 Jan 2026 and was reviewed by Aleksey Shipilev and Tobias Hartmann.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-vy-7e18de13-jdk26:backport-vy-7e18de13-jdk26
$ git checkout backport-vy-7e18de13-jdk26
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-vy-7e18de13-jdk26

⚠️ @vy You are not yet a collaborator in my fork openjdk-bots/jdk. An invite will be sent out and you need to accept it before you can proceed.