-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize PointerInvoke to benchmark by-ref segment return #788
Generalize PointerInvoke to benchmark by-ref segment return #788
Conversation
Results I got:
Passing segments as arguments works fine, but returning segments generate allocation. This seems to be unrelated to latest API changes - (even when I tweaked the FFM impl to always use global scope, the allocation seems to be still there). |
👋 Welcome back mcimadamore! A progress list of the required criteria for merging this PR into |
Webrevs
|
Doh - realized that my benchmark was escaping segments "by design" (since the benchmark methods were returning the segments). I've tweaked the benchmark to return the
None of the benchmark shows allocation now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice beef up!
@mcimadamore 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:
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 no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit e3a46c9. |
@mcimadamore Pushed as commit e3a46c9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
I've generalized an existing benchmark to test by-reference segment return in downcalls.
Ideally, we should see scalarization of the returned segment, and no GC activity.
Progress
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/panama-foreign pull/788/head:pull/788
$ git checkout pull/788
Update a local copy of the PR:
$ git checkout pull/788
$ git pull https://git.openjdk.org/panama-foreign pull/788/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 788
View PR using the GUI difftool:
$ git pr show -t 788
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/panama-foreign/pull/788.diff