8288840: StructureViolationException should not link to fork method

[AlanBateman]

StructureViolationException has a @see link to a fork method that does not throw this exception. The link should be removed for JDK 19. We'll add the link back once the JEP for Extent-Local Variables is integrated.

---

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-8288840: StructureViolationException should not link to fork method

Reviewers

• Paul Sandoz (@PaulSandoz - Reviewer)
• Mandy Chung (@mlchung - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 52

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19/pull/52.diff

[bridgekeeper]

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

@AlanBateman To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels

• build
• client
• compiler
• core-libs
• hotspot
• hotspot-compiler
• hotspot-gc
• hotspot-jfr
• hotspot-runtime
• i18n
• ide-support
• javadoc
• jdk
• jmx
• kulla
• net
• nio
• security
• serviceability
• shenandoah

[AlanBateman]

/label add core-libs

[openjdk]

@AlanBateman
The core-libs label was successfully added.

[mlbridge]

Webrevs

• 00: Full (6cf7ae79)

[openjdk]

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

8288840: StructureViolationException should not link to fork method

Reviewed-by: psandoz, mchung

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

• e26d3b3: 8288497: add support for JavaThread::is_oop_safe()
• c74a923: 8288531: Empty spans in mobile navigation markup
• af05139: 8288467: remove memory_operand assert for spilled instructions

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.

[AlanBateman]

/integrate

[openjdk]

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

• 7cf71bc: 8287982: Concurrent implicit attach from native threads crashes VM
• 9e2d9ac: 8288529: broken link in java.xml
• 70008da: 8287971: Throw exception for missing values in .jpackage.xml
• d7b43af: 8288761: SegmentAllocator:allocate(long bytesSize) not throwing IAEx when bytesSize < 0
• 834d92d: 8288754: GCC 12 fails to build zReferenceProcessor.cpp
• 198cec9: 8286103: VThreadMonitorTest fails "assert(!current->cont_fastpath() || (current->cont_fastpath_thread_state() && !interpreted_native_or_deoptimized_on_stack(current))) failed"
• 97200a7: 8278053: serviceability/jvmti/vthread/ContStackDepthTest/ContStackDepthTest.java failing in loom repo with Xcomp
• 31d981e: 8288532: additional review changes for JDK-8286830
• a144988: 8288139: JavaThread touches oop after GC barrier is detached
• e26d3b3: 8288497: add support for JavaThread::is_oop_safe()
• ... and 2 more: https://git.openjdk.org/jdk19/compare/b9c396625cc3fcddb89f93255f85f73a931acc34...master

Your commit was automatically rebased without conflicts.

[openjdk]

@AlanBateman Pushed as commit 8fa46c8.

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