8271611: Use SecurityConstants.ACCESS_PERMISSION in MethodHandles

[cl4es]

Reusing SecurityConstants.ACCESS_PERMISSION (which was moved from AccessibleObject by JDK-8202419) avoids initialization of ReflectPermission when no SecurityManager is installed

---

Progress

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

Issue

• JDK-8271611: Use SecurityConstants.ACCESS_PERMISSION in MethodHandles

Reviewers

• Roger Riggs (@RogerRiggs - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4957/head:pull/4957
$ git checkout pull/4957

Update a local copy of the PR:
$ git checkout pull/4957
$ git pull https://git.openjdk.java.net/jdk pull/4957/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 4957

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4957.diff

[bridgekeeper]

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

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

• core-libs

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

[RogerRiggs]

LGTM

[openjdk]

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

8271611: Use SecurityConstants.ACCESS_PERMISSION in MethodHandles

Reviewed-by: rriggs

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:

• 249d641: 8263561: Re-examine uses of LinkedList
• 6a3f834: 8268113: Re-use Long.hashCode() where possible
• 2536e43: 8270160: Remove redundant bounds check from AbstractStringBuilder.charAt()
• 6c4c48f: 8266972: Use String.concat() in j.l.Class where invokedynamic-based String concatenation is not available
• 72145f3: 8269665: Clean-up toString() methods of some primitive wrappers

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[cl4es]

Thanks for the review @RogerRiggs!

/integrate

[openjdk]

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

• e74537f: 8271605: Update JMH devkit to 1.32
• 249d641: 8263561: Re-examine uses of LinkedList
• 6a3f834: 8268113: Re-use Long.hashCode() where possible
• 2536e43: 8270160: Remove redundant bounds check from AbstractStringBuilder.charAt()
• 6c4c48f: 8266972: Use String.concat() in j.l.Class where invokedynamic-based String concatenation is not available
• 72145f3: 8269665: Clean-up toString() methods of some primitive wrappers

Your commit was automatically rebased without conflicts.

[openjdk]

@cl4es Pushed as commit 7a4c754.

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