Tell GCC to optimize for code size in some .c files #2202
Merged
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
fredrik-johansson
force-pushed
the
osize
branch
from
912400a to
4c363e1
Compare
|
@albinahlback Does this look OK? |
|
Yes! |
|
Perhaps this was not the best solution. For optimizations, Clang does not work like GCC as it will not accept these things. One should really push |
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.
Some files have large chunks of code that don't need to be optimized for execution speed, so it makes sense to selectively compile with -Os.
This shrinks my libflint.so by 300 KB.