Add inlining code-size measurements for the 13 benchmarks - #87
Merged
Conversation
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
1 participant
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.
Adds
results/inlining.csv: per-benchmark.textsize at O3 with the shippedFORCE_INLINE = always_inlinesources versusFORCE_INLINE = static inline(letting O3's inliner decide), for the 13 benchmarks inresults/. Measured withckpt compile uninstrumented --no-device-debugandmsp430-elf-size; the last column lists the functions O3 leaves out of line.Summary: O3 already inlines every function on 8/13 (3 byte-identical, the rest within −0.9% to +13.3% from pass ordering); on the other 5 forced inlining grows code by 4.1–126.4%, at most 4.2 kB (sha256), 1.6% of the 256 kB FRAM.