diff options
author | Daniel Mueller <deso@posteo.net> | 2019-01-07 13:59:08 -0800 |
---|---|---|
committer | Daniel Mueller <deso@posteo.net> | 2019-01-07 13:59:08 -0800 |
commit | fbb307551de0d26e612d1b00f386ccf45d84b066 (patch) | |
tree | 29e1731890494ae04f4e476b45df5f701f5d98d7 /libc/ci/docker/powerpc64-unknown-linux-gnu | |
parent | 790e84091e10d52d2dd33aab7400b5d6345200a7 (diff) | |
download | nitrocli-fbb307551de0d26e612d1b00f386ccf45d84b066.tar.gz nitrocli-fbb307551de0d26e612d1b00f386ccf45d84b066.tar.bz2 |
Switch to using the system allocator
In the past we have already taken a couple of steps to reduce the size
of the final binary, arguing that binary size is the metric of most
relevance for the program at hand:
- the memory footprint is close to irrelevant because the program does
not stay resident in memory for long
- execution speed is likely dominated by communication with the Nitrokey
itself, which is a slow I/O device
With that in mind, this change decreases the binary size further by
swapping the default allocator we use (typically jemalloc) with the
system allocator (which is malloc based on Unix systems). Given that we
are by no means allocation sensitive, there is no point in wasting
binary size on something that adds no value.
This change decreases the binary size by another 324 KiB (for an already
stripped release mode binary).
Diffstat (limited to 'libc/ci/docker/powerpc64-unknown-linux-gnu')
0 files changed, 0 insertions, 0 deletions