8337783: Use THROW_NULL instead of THROW_0 in pointer contexts in misc runtime code

[kimbarrett]

Please review this trivial change that, in misc. runtime code where a pointer
value is required, replaces uses of THROW_0 and THROW_MSG_0 with THROW_NULL
and THROW_MSG_NULL respectively.

Testing: mach5 tier1

---

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-8337783: Use THROW_NULL instead of THROW_0 in pointer contexts in misc runtime code (Enhancement - P4)

Reviewers

• Stefan Karlsson (@stefank - Reviewer)
• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 20457

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

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

8337783: Use THROW_NULL instead of THROW_0 in pointer contexts in misc runtime code

Reviewed-by: stefank, shade

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

• c095c0e: 8336489: Track scoped accesses in JVMCI compiled code
• 7e925d7: 8337283: configure.log is truncated when build dir is on different filesystem
• 2e093b0: 8337779: test/jdk/jdk/jfr/jvm/TestHiddenWait.java is a bit fragile
• d3e7b0c: 8336462: ConcurrentSkipListSet Javadoc incorrectly warns about size method complexity
• be34730: 8335257: Refactor code to create Initialized Assertion Predicates into separate class
• fbe8a81: 8333144: docker tests do not work when ubsan is configured
• dabdae6: 8334599: Improve code from JDK-8302671
• 8bd3cd5: 8337716: ByteBuffer hashCode implementations are inconsistent

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.

[openjdk]

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

• hotspot

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 (4c81d973)

[stefank]

Looks good.

I saw at least one instance of THROW_ARG_0, which returns 0. Do you intend to fix that as a separate change?

[shipilev]

Current changes look okay. Same as in other PR, I have not checked these caught all the instances of THROW_* in those files.

[kimbarrett]

Looks good.

I saw at least one instance of THROW_ARG_0, which returns 0. Do you intend to fix that as a separate change?

Yes. There are a few of those scattered about. We don't currently have THROW_ARG_NULL to use in these places.
I chose to keep this change simple.

[kimbarrett]

Thanks for reviews @shipilev and @stefank

[kimbarrett]

/integrate

[openjdk]

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

• 431d4f7: 8337785: Fix simple -Wzero-as-null-pointer-constant warnings in x86 code
• e2c07d5: 8337299: vmTestbase/nsk/jdb/stop_at/stop_at002/stop_at002.java failure goes undetected
• 08f697f: 8337819: Update GHA JDKs to 22.0.2
• 42652b2: 8337787: Fix -Wzero-as-null-pointer-constant warnings when JVMTI feature is disabled
• 807186f: 8337784: Fix simple -Wzero-as-null-pointer-constant warnings in linux/posix code
• e68df52: 8337054: JDK 23 RDP2 L10n resource files update
• 9856216: 8336928: GHA: Bundle artifacts removal broken
• 219e1eb: 8337712: Wrong javadoc in java.util.Date#toString(): "61" and right parenthesis
• 97afbd9: 8336410: runtime/NMT/TotalMallocMmapDiffTest.java Total malloc diff is incorrect. Expected malloc diff range
• c095c0e: 8336489: Track scoped accesses in JVMCI compiled code
• ... and 7 more: https://git.openjdk.org/jdk/compare/367e0a65561f95aad61b40930d5f46843fee3444...master

Your commit was automatically rebased without conflicts.

[openjdk]

@kimbarrett Pushed as commit 7146dae.

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