-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Bump libffi #5779
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
Bump libffi #5779
Conversation
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.
Please rebase it
e5e0a22
to
f442e67
Compare
@youknowone fixed. |
f442e67
to
3480f36
Compare
Cargo.lock is removed |
Closed by mistake. |
Cargo.lock must not be removed |
3480f36
to
7ac9a1e
Compare
@youknowone fixed |
Also remove system feature from jit libffi, as that forces libffi to be installed on the system
7ac9a1e
to
cf37fba
Compare
WalkthroughThe updates involve modifying the Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
Cargo.toml (1)
172-172
: Bump libffi to 4.1 — verify and unify
Ensure the new 4.1 release exists on crates.io, update and commit yourCargo.lock
(cargo update -p libffi --precise 4.1
), and confirm all CI pipelines pass. For consistency across workspace crates, consider adding a[patch.crates-io]
override at the workspace root to enforce libffi v4.1.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
Cargo.toml
(1 hunks)jit/Cargo.toml
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (11)
- GitHub Check: Run rust tests (ubuntu-latest)
- GitHub Check: Run snippets and cpython tests (macos-latest)
- GitHub Check: Run snippets and cpython tests (ubuntu-latest)
- GitHub Check: Check the WASM package and demo
- GitHub Check: Run snippets and cpython tests (windows-latest)
- GitHub Check: Run tests under miri
- GitHub Check: Check Rust code with rustfmt and clippy
- GitHub Check: Run rust tests (macos-latest)
- GitHub Check: Run rust tests (windows-latest)
- GitHub Check: Run snippets and cpython tests on wasm-wasi
- GitHub Check: Ensure compilation on various targets
🔇 Additional comments (1)
jit/Cargo.toml (1)
18-18
: Removesystem
feature from libffi — confirm default linking
Dropping thesystem
feature simplifies the JIT build, but verify that the default feature set of the libffi crate still compiles and links correctly on Linux, macOS, and Windows.
Also remove system feature from JIT, as that forces libffi to be installed on the system and doesn't have a real benefit.
Summary by CodeRabbit