-
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
8276136: functional interface extraction broken after API refresh #605
8276136: functional interface extraction broken after API refresh #605
Conversation
👋 Welcome back mcimadamore! A progress list of the required criteria for merging this PR into |
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.
LGTM
@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 122 new commits pushed to the
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 |
/integrate |
Going to push as commit ac0b4a1.
Your commit was automatically rebased without conflicts. |
@mcimadamore Pushed as commit ac0b4a1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This addresses the issue discovered in this thread:
https://mail.openjdk.java.net/pipermail/panama-dev/2021-September/015144.html
The issue is causes by the fact that the new linker changes introduce an asymmetry between the method type of the downcall and that of an upcall. Downcall have
Addressable
for parameters passed by-reference, andMemoryAddress
for by-reference returns. Upcalls adopt the dual scheme (MemoryAddress
for parameters,Addressable
for return values).This patch bridges the two schemes by inserting the required casts which keep
invokeExact
happy in the case where we generate a functional interface implementation which calls the upcall stub address.To do that I had to dig a bit in
TypeTranslator
to make the type translation context-dependent. I also had to enhanceFunctionInfo
so that it could carry the "reverse" method type in the upcall case.I've added a test which checks a function pointer which takes an address and returns another address - which stresses both argument and return mismatch.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/panama-foreign pull/605/head:pull/605
$ git checkout pull/605
Update a local copy of the PR:
$ git checkout pull/605
$ git pull https://git.openjdk.java.net/panama-foreign pull/605/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 605
View PR using the GUI difftool:
$ git pr show -t 605
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/panama-foreign/pull/605.diff