public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: Philip.Blundell@pobox.com (Philip Blundell)
Cc: scottb@netwinder.org (scottb), libc-hacker@sourceware.cygnus.com
Subject: Re: static executable bloat
Date: Sun, 22 Aug 1999 09:20:00 -0000	[thread overview]
Message-ID: <19990822161923.02C3A8EEE@ocean.lucon.org> (raw)
In-Reply-To: <E11IKRR-0000WO-00@kings-cross.london.uk.eu.org>

> 
> >#include <stdio.h>
> >int main(int argc, char **argv)
> >{
> >  printf ("Hello World\n");
> >}
> >
> >compiles to 985,018 bytes.  This is almost all libc overhead.
> >Most of which is never going to be needed.
> 
> Yes, it is a bit sad.  Somewhere I have some half-baked patches that allow you 
> to stub out the majority of the gconv and wchar code at configure time; I did 
> this for an internal project where the resulting binaries had to fit into ROM.
> 
> The other thing I looked at was dropping the stdio implementation from newlib 
> (which is far less featureful but also a whole lot smaller) into libc.  I 
> think I got that to mostly work and again I can probably dig out some patches 
> if anyone is interested.
> 

May I ask if it is ok to add some flags to get a smaller static
binary without gconv and/or wchar support? I am thinking to write
libNoGconv.a and libNoWchar.a. People can stub out gconv and/or wchar
with

# gcc -static .... -lNoGconv -lNoWchar

Will that work for people who want smaller static binaries or do you
want smaller static binaries with supports for everything?


-- 
H.J. Lu (hjl@gnu.org)

  reply	other threads:[~1999-08-22  9:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-19  0:29 Zack Weinberg
1999-08-19  5:24 ` Andreas Schwab
1999-08-19  9:39   ` Roland McGrath
1999-08-19  9:57     ` Ulrich Drepper
1999-08-19 11:04       ` Roland McGrath
1999-08-19 11:08         ` Ulrich Drepper
1999-08-19 14:59           ` Thorsten Kukuk
1999-08-19 15:06             ` Ulrich Drepper
1999-08-19 15:17               ` Thorsten Kukuk
1999-08-19 15:41                 ` Ulrich Drepper
1999-08-20  7:20                   ` scottb
1999-08-21 16:21                     ` Philip Blundell
1999-08-22  9:20                       ` H.J. Lu [this message]
1999-08-22 10:06                         ` Ulrich Drepper
1999-08-22 10:11                           ` H.J. Lu
1999-08-22 10:44                             ` Ulrich Drepper
1999-08-22 11:05                         ` Philip Blundell
1999-08-21 17:57                   ` Cristian Gafton
1999-08-21 17:56                 ` Cristian Gafton
1999-08-21 17:54               ` Cristian Gafton
1999-08-19 17:45           ` Geoff Keating
1999-08-19 17:49             ` Ulrich Drepper
1999-08-19  9:57   ` Zack Weinberg

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=19990822161923.02C3A8EEE@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=Philip.Blundell@pobox.com \
    --cc=libc-hacker@sourceware.cygnus.com \
    --cc=scottb@netwinder.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).