-
Notifications
You must be signed in to change notification settings - Fork 0
Feature/32bit release targets #3
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
44a8b46
ci: add 32-bit linux/windows targets to release builds
Athemis bcfbb1c
ci: add i586 Linux target to release workflow
Athemis b2bf9cc
ci: sanitize ref names in release artifacts
Athemis cd3734f
ci: fix release artifact naming with safe ref env
Athemis a5ba25b
ci: update release builds
Athemis 29151c5
ci: rely on cargo strip and drop workflow strip step
Athemis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🧩 Analysis chain
🌐 Web query:
Rust Cargo profile.release lto "thin" string syntax stable version💡 Result:
Yes — Cargo accepts the string form lto = "thin" in [profile.*] on stable Rust. The Cargo reference lists "thin" as a valid lto value (alongside true/"fat", false, and "off"). [1][2]
Example:
[profile.release]
lto = "thin"
Sources:
[1] Cargo Book — Profiles (official reference).
[2] Rust/Cargo docs showing LTO enum/values.
🌐 Web query:
Rust Cargo profile strip "symbols" setting stable version💡 Result:
The Cargo profile
stripoption (so you can use values like "symbols") was stabilized in Rust 1.59.0. [1][2]Sources:
stripprofile option"). [2]Optimize release profile with thin LTO and symbol stripping—verify toolchain version.
The changes employ thin LTO and full symbol stripping, which represent a sensible tradeoff: reduced build time and smaller binaries at the cost of diminished post-mortem debuggability. Both
lto = "thin"andstrip = "symbols"are stable Rust features, though they require a sufficiently recent toolchain. Ensure your Rust version is 1.59 or later to support these profile settings.Consider whether the transition from
strip = "debuginfo"tostrip = "symbols"aligns with your production support posture. Full symbol stripping will complicate crash analysis and customer support scenarios.🤖 Prompt for AI Agents