summaryrefslogtreecommitdiff
path: root/rand/rand_jitter
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-16 18:58:32 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-16 18:58:32 -0800
commit4cf1b0c003a8bd0214e548a77bf0336148235931 (patch)
treeb5179deb570aef2f056c01284666f1daa1080798 /rand/rand_jitter
parent6cae9704af80f6ffbca2770c5bbf9ab94ef846f8 (diff)
downloadnitrocli-4cf1b0c003a8bd0214e548a77bf0336148235931.tar.gz
nitrocli-4cf1b0c003a8bd0214e548a77bf0336148235931.tar.bz2
Add a script to determine the nitrocli binary size at a git revision
We have been loosely tracking the resulting size of the stripped release binary as that is arguably the most relevant metric to optimize for. To have a better idea of the influence of various changes and their effect on the binary size, this change adds a script that automates the process of gathering this metric. E.g., $ var/binary-size.py HEAD~3 HEAD --unit kib > 994 > 970
Diffstat (limited to 'rand/rand_jitter')
0 files changed, 0 insertions, 0 deletions