AoT builds: use -O3 optimization level#202
Merged
Karolina-Bogacka merged 1 commit intomainfrom Aug 25, 2025
Merged
Conversation
Karolina-Bogacka
approved these changes
Aug 25, 2025
Collaborator
Karolina-Bogacka
left a comment
There was a problem hiding this comment.
I do agree with the priorities here
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue #195
Change compiler options to optimize for speed, instead of size. This should lead to more aggressive inlining, which greatly benefits Jelly, but will also inevitably increase the binary size.
This does increase the binary size by quite a bit (up to 63M uncompressed), but compared with the latest release (
jelly-cli-os), when compressed that's just 6MB more:With -Os (baseline):
With -O3:
So, it also increased throughput by almost 2x. I think that's worth the extra few megabytes, especially because jelly-cli users mostly care about throughput...