From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>, Denys Vlasenko <vda.linux@googlemail.com>
Subject: Re: [PATCH] configure: add gcc flags for better link-time optimization
Date: Fri, 23 Oct 2015 15:12:02 +0200 [thread overview]
Message-ID: <20151023131202.GI10551@port70.net> (raw)
In-Reply-To: <1445603426-4827-1-git-send-email-vda.linux@googlemail.com>
* Denys Vlasenko <vda.linux@googlemail.com> [2015-10-23 14:30:26 +0200]:
> libc.so size reduction:
>
> text data bss dec hex filename
> 564099 1944 11768 577811 8d113 libc.so.before
> 562277 1924 11576 575777 8c921 libc.so
>
i assume this is x86_64, nice improvement.
> +# When linker merges sections, a tiny section (such as one resulting
> +# from "static char flag_var") with no alignment restrictions
> +# can end up logded between two more strongly aligned ones (say,
> +# "static int global_cnt1/2", both of which want 32-bit alignment).
> +# Then this byte-sized "flag_var" gets 3 bytes of padding.
> +#
> +# With section sorting by alignment, one-byte flag variables have
> +# higher chance of being grouped together and not require padding.
> +# (It can be made even better. Linker is too dumb.
> +# ld needs to grow -Wl,--pack-sections-optimally)
> +#
> +# For us, this affects the size of only one file: libc.so
> +#
> +tryldflag LDFLAGS_AUTO -Wl,--sort-section=alignment
> +tryldflag LDFLAGS_AUTO -Wl,--sort-common
i think this came up before
https://sourceware.org/bugzilla/show_bug.cgi?id=14156
it was also noted at some point that the optimal sorting
is 'sort by use' so all the unused legacy functions end
up on the same page so they never need to be loaded.
probably config knobs would be useful that turn off libc
features, but not by dropping them, just moving them to a
different part of libc.so that is assumed to be never needed.
next prev parent reply other threads:[~2015-10-23 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 12:30 Denys Vlasenko
2015-10-23 13:12 ` Szabolcs Nagy [this message]
2015-10-23 14:41 ` Denys Vlasenko
2015-10-23 14:48 ` Rich Felker
2015-10-23 22:00 ` Denys Vlasenko
2015-10-24 12:43 ` Szabolcs Nagy
2015-10-24 19:20 ` Rich Felker
2015-10-27 1:21 ` Rich Felker
2015-10-27 19:09 ` Denys Vlasenko
2015-10-27 21:01 ` Rich Felker
2015-10-28 9:53 ` Denys Vlasenko
2015-10-28 10:05 ` Denys Vlasenko
2015-11-01 19:56 ` Rich Felker
2015-11-02 22:36 ` Rich Felker
2015-11-03 0:01 ` Rich Felker
2015-11-05 2:58 ` Rich Felker
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=20151023131202.GI10551@port70.net \
--to=nsz@port70.net \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
--cc=vda.linux@googlemail.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).