From: Denys Vlasenko <vda.linux@googlemail.com>
To: Rich Felker <dalias@libc.org>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
musl <musl@lists.openwall.com>
Subject: [PATCH] configure: add gcc flags for better link-time optimization
Date: Fri, 23 Oct 2015 14:30:26 +0200 [thread overview]
Message-ID: <1445603426-4827-1-git-send-email-vda.linux@googlemail.com> (raw)
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
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
CC: musl <musl@lists.openwall.com>
---
configure | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/configure b/configure
index 4564ad8..a9ed159 100755
--- a/configure
+++ b/configure
@@ -440,6 +440,44 @@ tryflag CFLAGS_AUTO -fno-unwind-tables
tryflag CFLAGS_AUTO -fno-asynchronous-unwind-tables
#
+# 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
+
+#
+# Put every function and data object into its own section:
+# .text.funcname, .data.var, .rodata.const_struct, .bss.zerovar
+#
+# Previous optimization isn't working too well by itself
+# because data objects aren't living in separate sections,
+# they are all grouped in one .data and one .bss section per *.o file.
+# With -ffunction/data-sections, section sorting eliminates more padding.
+#
+# Object files in static *.a files will also have their functions
+# and data objects each in its own section.
+#
+# This enables programs statically linked with -Wl,--gc-sections
+# to perform "section garbage collection": drop unused code and data
+# not on per-*.o-file basis, but on per-function and per-object basis.
+# This is a big thing: --gc-sections sometimes eliminates several percent
+# of unreachable code and data in final executable.
+#
+tryflag CFLAGS_AUTO -ffunction-sections
+tryflag CFLAGS_AUTO -fdata-sections
+
+#
# The GNU toolchain defaults to assuming unmarked files need an
# executable stack, potentially exposing vulnerabilities in programs
# linked with such object files. Fix this.
--
1.8.1.4
next reply other threads:[~2015-10-23 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 12:30 Denys Vlasenko [this message]
2015-10-23 13:12 ` Szabolcs Nagy
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=1445603426-4827-1-git-send-email-vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=dalias@libc.org \
--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).