From: Jorge Almeida <jjalmeida@gmail.com>
To: musl@lists.openwall.com
Subject: size of executable
Date: Mon, 12 Aug 2019 17:48:24 +0100 [thread overview]
Message-ID: <CAKpSnpK2XsepQ-AVO9+7HGrNAK+1YFRv=x56K6QOpK0egjcnAg@mail.gmail.com> (raw)
I think my executables are way too large. They used to be much
smaller, not so long ago (e.g. 18 months ago). I'm using musl 1.1.23
with gcc-8.3.0 on x86_64. Could someone check the following hello.c
and see what size you get?
I get 16768 bytes (not stripped) and 12324 (stripped).
Note that I'm not even using printf.
Thanks
#include <unistd.h>
int main(int argc, char* argv[]){
write(1, "Hello, bloated world...\n", 24);
}
next reply other threads:[~2019-08-12 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 16:48 Jorge Almeida [this message]
2019-08-12 16:55 ` Jorge Almeida
2019-08-12 17:18 ` Rich Felker
2019-08-12 17:59 ` Jorge Almeida
2019-08-12 18:16 ` Khem Raj
2019-08-12 18:23 ` Rich Felker
2019-08-13 10:15 ` Micha Nelissen
2019-08-13 11:45 ` Fangrui Song
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='CAKpSnpK2XsepQ-AVO9+7HGrNAK+1YFRv=x56K6QOpK0egjcnAg@mail.gmail.com' \
--to=jjalmeida@gmail.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).