Skip to content
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

[Feature Request] Enable Link-Time Optimization (LTO) #128

Open
zamazan4ik opened this issue Oct 20, 2024 · 0 comments
Open

[Feature Request] Enable Link-Time Optimization (LTO) #128

zamazan4ik opened this issue Oct 20, 2024 · 0 comments
Labels
type: feature New feature or request

Comments

@zamazan4ik
Copy link

Describe the problem/motivation

Motivation: improve the binary size and, possibly, gain a bit of additional performance (but the binary size is the main motivation in this case).

Describe the solution you'd like

I suggest enabling LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional dist or release-lto profile where additionally to regular release optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application. Using ThinLTO should also help to reduce the build-time overhead with LTO. If we enable it on the Cargo profile level, users, who install the application with cargo install, will get the LTO-optimized version "automatically". E.g., check cargo-outdated Release profile.

Basically, it can be enabled with the following lines:

[profile.release]
lto = true

I have made quick tests on my local setup (Fedora 40, Rustc 1.82): enabling lto = true for the Release profile reduces the binary size from 28 Mib to 20 Mib.

Alternatives considered

Leave the things as is

@zamazan4ik zamazan4ik added the type: feature New feature or request label Oct 20, 2024
@github-project-automation github-project-automation bot moved this to 📬 Needs triage in zebar Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature or request
Projects
Status: 📬 Needs triage
Development

No branches or pull requests

1 participant