public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: libc-alpha@sourceware.org
Cc: Vincent.Lefevre@ens-lyon.fr
Subject: massive increase of the size of the library
Date: Tue, 21 Jul 2020 10:22:29 +0200	[thread overview]
Message-ID: <mwo8o9cm62.fsf@tomate.loria.fr> (raw)

       Hi,

some user reported us that the size of the MPFR library did increase a lot
between 4.0.2 and 4.1.0. I notice a similar fact for the GNU libc, between
2.28 and 2.29, both for libc.a and libc.so (the same holds for libm.a and
libm.so):

-rw-r--r-- 1 zimmerma caramba  5121680 May 20 10:49 /localdisk/zimmerma/glibc-2.28/build/libc.a
-rw-r--r-- 1 zimmerma caramba 45919382 Mar  6 07:58 /localdisk/zimmerma/glibc-2.29/build/libc.a

-rwxr-xr-x 1 zimmerma caramba  2092096 May 20 11:07 /localdisk/zimmerma/glibc-2.28/build/libc.so
-rwxr-xr-x 1 zimmerma caramba 18769880 Mar  6 07:58 /localdisk/zimmerma/glibc-2.29/build/libc.so

We see an increase in size by a factor of almost 10!

2.28 was configured with --without-selinux, but if I configure 2.29 with
--without-selinux, I get similar figures as the 2.29 ones above. Also 2.28 was
compiled with gcc 9.3.0, whereas 2.29 was compiled with gcc 9.2.1, but
compiling 2.29 with gcc 9.3.0 does not change much too.

Does anybody know the reason of that massive increase?

Paul


             reply	other threads:[~2020-07-21  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  8:22 Paul Zimmermann [this message]
2020-07-21  8:26 ` Florian Weimer
2020-07-21  8:36   ` Paul Zimmermann
2020-07-21  8:40     ` Florian Weimer
2020-07-21  8:54       ` Paul Zimmermann
2020-07-21 19:37         ` Joseph Myers
2020-07-21  8:45     ` Andreas Schwab

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=mwo8o9cm62.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=Vincent.Lefevre@ens-lyon.fr \
    --cc=libc-alpha@sourceware.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).