8364461: JFR: Default constructor may not be first in setting control

[egahlin]

Could I have a review of a PR that fixes a bug occurring when a user-defined setting does not have the default constructor first?

Test: test/jdk/jdk/jfr

Thanks
Erik

---

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-8364461: JFR: Default constructor may not be first in setting control (Bug - P4)

Reviewers

• Markus Grönlund (@mgronlun - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26582

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8364461: JFR: Default constructor may not be first in setting control

Reviewed-by: mgronlun

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

• ee3665b: 8364187: Make getClassAccessFlagsRaw non-native
• 2ba8a06: 8348868: AArch64: Add backend support for SelectFromTwoVector
• 8ac4a88: 8362237: IllegalArgumentException in the launcher when exception without stack trace is thrown
• ... and 14 more: https://git.openjdk.org/jdk/compare/fe09e93b8fc3081c944f3824fdaa55cc17e377a8...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]

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

• hotspot-jfr

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 (12599f98)

[egahlin]

/integrate

[openjdk]

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

• 3bc4497: 8364258: ThreadGroup constant pool serialization is not normalized
• cf5a255: 8364427: JFR: Possible resource leak in Recording::getStream
• ea7e943: 8364257: JFR: User-defined events and settings with a one-letter name cannot be configured
• ... and 29 more: https://git.openjdk.org/jdk/compare/fe09e93b8fc3081c944f3824fdaa55cc17e377a8...master

Your commit was automatically rebased without conflicts.

[openjdk]

@egahlin Pushed as commit b96b9c3.

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