This is the mail archive of the
mailing list for the glibc project.
Re: Statically linked binary way way too big
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Roland McGrath <roland at redhat dot com>
- Cc: "Martin v. Loewis" <martin at v dot loewis dot de>, vda at port dot imtp dot ilyichevsk dot odessa dot ua, libc-alpha at sources dot redhat dot com
- Date: Wed, 16 Oct 2002 17:51:52 +0200
- Subject: Re: Statically linked binary way way too big
- References: <firstname.lastname@example.org> <200210161548.g9GFmLR01796@magilla.sf.frob.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Wed, Oct 16, 2002 at 08:48:21AM -0700, Roland McGrath wrote:
> > It can, if the module has been compiled with
> > -ffunction-sections. However, for glibc, this is not an issue, because
> > no module contains more than one function.
> This is not true, though ideally it should be. The worst offender is
> malloc, which is all in one huge module and so all the unused cruft gets
> linked into every static program. This is truly unacceptable because
> malloc_stats calls fprintf and so the malloc module brings in all of stdio.
Yeah, malloc_stats should be surely put into a separate file.