Produce releases with Interprocedural optimisations (LTO) #2187
Conversation
This file contains 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
piponazo
requested review from
clanmills,
neheb,
kevinbackhouse,
kmilos,
hassec and
postscript-dev
Codecov Report
@@ Coverage Diff @@
## main #2187 +/- ##
==========================================
- Coverage 63.30% 63.29% -0.02%
==========================================
Files 99 99
Lines 19596 19596
Branches 9559 9559
==========================================
- Hits 12406 12404 -2
- Misses 5116 5118 +2
Partials 2074 2074
Continue to review full report at Codecov.
|
kevinbackhouse
approved these changes
Apr 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As I mentioned at #2184 , it has some benefits to use Link-Time Optimisations when generating the binaries, in terms of speed and size.
By studying how different settings affect to the final size of the binaries (static libs, dynamic ones and executables) I realised that we actually do not need to deploy in our tarballs the
exiv2-xmptarget that was being treated as a STATIC library. By treating that target as a OBJECT library, we will not need to deploy it separately. The object code needed bylibexiv2will be incorporated in the shared lib.You can compare the latest nightly build (without LTO) and the build with LTO.
As always, any feedback is welcome!