From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, Vincent.Lefevre@ens-lyon.fr
Subject: Re: massive increase of the size of the library
Date: Tue, 21 Jul 2020 10:54:15 +0200 [thread overview]
Message-ID: <mwimehckp4.fsf@tomate.loria.fr> (raw)
In-Reply-To: <87lfjds1le.fsf@oldenburg2.str.redhat.com> (message from Florian Weimer on Tue, 21 Jul 2020 10:40:13 +0200)
> From: Florian Weimer <fweimer@redhat.com>
> Date: Tue, 21 Jul 2020 10:40:13 +0200
>
> * Paul Zimmermann:
>
> > sure, the files are here:
> >
> > https://members.loria.fr/PZimmermann/libc-2.28.a
> > https://members.loria.fr/PZimmermann/libc-2.28.so
> > https://members.loria.fr/PZimmermann/libc-2.29.a
> > https://members.loria.fr/PZimmermann/libc-2.29.so
>
> text data bss dec hex filename
> 1753624 20968 16408 1791000 1b5418 libc-2.28.so
> 1758304 20968 16408 1795680 1b6660 libc-2.29.so
>
> So the actual code is of the same size.
>
> The difference seems to be that the second file contains debugging
> information:
>
> $ strip libc-2.2?.so
> $ ls -l libc-2.2?.so
> -rw-rw-r--. 1 fweimer fweimer 1791400 Jul 21 10:39 libc-2.28.so
> -rw-rw-r--. 1 fweimer fweimer 1791400 Jul 21 10:39 libc-2.29.so
>
> So it must be a difference in your build environment.
>
> Thanks,
> Florian
thanks Florian. Indeed I had to compile 2.28 with CFLAGS="-O2 -Wno-error"
since with -Werror it does not compile with gcc 9.3.0. If I add -g then
I get a similar size than with 2.29 (where CFLAGS="-O2 -g" by default).
Paul
next prev parent reply other threads:[~2020-07-21 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 8:22 Paul Zimmermann
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 [this message]
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=mwimehckp4.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=Vincent.Lefevre@ens-lyon.fr \
--cc=fweimer@redhat.com \
--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).