8268103: JNI functions incorrectly return a double after JDK-8265836

[jerboaa]

Please review this trivial patch. Stubs should return -1 for jlong rather than -1.0 (double) on aix/macosx.

Thoughts?

---

Progress

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

Issue

• JDK-8268103: JNI functions incorrectly return a double after JDK-8265836

Reviewers

• David Holmes (@dholmes-ora - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 4300

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

Using diff file

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

[bridgekeeper]

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

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

• jmx
• serviceability

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 (2d3c01dc)

[tanghaoth90]

LGTM. Thanks!

[dholmes-ora]

Looks good and trivial.

Thanks,
David

[openjdk]

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

8268103: JNI functions incorrectly return a double after JDK-8265836

Reviewed-by: dholmes

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:

• 71425dd: 8267118: OutOfMemoryError cannot be caught as a Throwable
• de6472c: 8267459: Pasting Unicode characters into JShell does not work.
• 9247630: 8265270: Type.getEnclosingType() may fail with CompletionFailure
• 2d494bf: 8267836: Separate eager reclaim remembered set threshold from G1RSetSparseRegionEntries
• bba3728: 8267726: ZGC: array_copy_requires_gc_barriers too strict

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.

[jerboaa]

Thanks for the reviews!

[jerboaa]

/integrate

[openjdk]

@jerboaa Since your change was applied there have been 8 commits pushed to the master branch:

• 6765f90: 8266459: Implement JEP 411: Deprecate the Security Manager for Removal
• 19450b9: 8266281: Assign Symbols to the package selector expression
• a223189: 8264774: Implementation of Foreign Function and Memory API (Incubator)
• 71425dd: 8267118: OutOfMemoryError cannot be caught as a Throwable
• de6472c: 8267459: Pasting Unicode characters into JShell does not work.
• 9247630: 8265270: Type.getEnclosingType() may fail with CompletionFailure
• 2d494bf: 8267836: Separate eager reclaim remembered set threshold from G1RSetSparseRegionEntries
• bba3728: 8267726: ZGC: array_copy_requires_gc_barriers too strict

Your commit was automatically rebased without conflicts.

Pushed as commit 2963c9e.

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