-
Notifications
You must be signed in to change notification settings - Fork 463
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
8239095: Upgrade libFFI to the latest 3.3 version #242
Conversation
👋 Welcome back almatvee! A progress list of the required criteria for merging this PR into |
/reviewers 2 |
@kevinrushforth |
@arapte Can you review as well? |
Initial testing looks good. I'll finish my testing & review on Monday. |
@@ -50,7 +50,9 @@ | |||
#endif | |||
|
|||
#define FFI_TARGET_SPECIFIC_STACK_SPACE_ALLOCATION | |||
//#define FFI_TARGET_HAS_COMPLEX_TYPE |
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.
In the original release of libffi 3.2.1, this line is not commented. which means it was commented in JavaFX. I cannot trace when and why was it commented. Should it be reasoned to whether enable it or not ?
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.
That's a good question. The commented line was there from the first commit (in 9, changeset 9231:241f9696e3ad, https://bugs.openjdk.java.net/browse/JDK-8043352) but I don't see a reason on why it was disabled.
libffi is also built in the GraalVM project, and that line is not commented there.
@sashamatveev or @kevinrushforth do you remember the reason?
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.
No, I don't remember.
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.
No, I don't remember as well.
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.
I tested this and couldn't find issues. The uncommented line worries me a bit, though, but I can't see a reason why it should be commented again.
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.
Looks good to me.
@sashamatveev This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type
Since the source branch of this PR was last updated there have been 7 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 automatic rebasing, please merge ➡️ To integrate this PR with the above commit message to the |
/integrate |
@sashamatveev The following commits have been pushed to master since your change was applied:
Your commit was automatically rebased without conflicts. Pushed as commit 6bd0e22. |
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jfx pull/242/head:pull/242
$ git checkout pull/242