From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: Size comparison of an executable compiled for different targets.
Date: Sat, 27 Sep 2014 12:07:39 -0500 [thread overview]
Message-ID: <5426EEDB.6060302@pennware.com> (raw)
Here is a size comparison of compiling bzip2 for different targets using the
ELLCC clang/LLVM based cross development tool chain (http://ellcc.org):
-target Endian Float
armeb-linux-engeabi Big Soft
armeb-linux-engeabihf Big Hard
arm-linux-engeabi Little Soft
arm-linux-engeabihf Little Hard
i386-linux-eng Little Hard
mipsel-linux-eng Little Hard
mipsel-linux-engsf Little Soft
mips-linux-eng Big Hard
mips-linux-engsf Big Soft
ppc-linux-eng Big Hard
x86_64-linux-eng Little Hard
/ellcc/test/src/bzip2-1.0.6] dev% size bzip2*-linux-*
text data bss dec hex filename
177316 3632 7828 188776 2e168 bzip2.armeb-linux-engeabi
170356 3632 7828 181816 2c638 bzip2.armeb-linux-engeabihf
177332 3632 7828 188792 2e178 bzip2.arm-linux-engeabi
170364 3632 7828 181824 2c640 bzip2.arm-linux-engeabihf
156750 3620 7812 168182 290f6 bzip2.i386-linux-eng
314676 3632 7820 326128 4f9f0 bzip2.microblaze-linux-eng
205476 3656 7900 217032 34fc8 bzip2.mipsel-linux-eng
213608 3656 7900 225164 36f8c bzip2.mipsel-linux-engsf
205492 3656 7900 217048 34fd8 bzip2.mips-linux-eng
213632 3656 7900 225188 36fa4 bzip2.mips-linux-engsf
180680 3632 7828 192140 2ee8c bzip2.ppc-linux-eng
164482 3992 8640 177114 2b3da bzip2.x86_64-linux-eng
Soft float adds about 7K to the size of the executable compared to its
hard float counterpart, which sounds about right. These executables are
all statically linked with musl and compiler-rt. A dynamically linked
executable
for x86_64 looks like this:
[~/ellcc/test/src/bzip2-1.0.6] dev% size bzip2
text data bss dec hex filename
120131 4176 4400 128707 1f6c3 bzip2
-Rich
reply other threads:[~2014-09-27 17:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5426EEDB.6060302@pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).