From: Andreas Schwab <schwab@suse.de>
To: Zack Weinberg <zack@bitmover.com>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: static executable bloat
Date: Thu, 19 Aug 1999 05:24:00 -0000 [thread overview]
Message-ID: <jezozoarhu.fsf@hawking.suse.de> (raw)
In-Reply-To: <199908190722.AAA30582@zack.bitmover.com>
Zack Weinberg <zack@bitmover.com> writes:
|> I spent a lot of time today bashing at this, but there is no easy fix.
|> I guess this is just a "libio should be smaller" whine. Note that an
|> awful lot of places in there know when a stream is wide; it seems to
|> me that this ought to be hidden in the jump table. There's no reason
|> why not to redirect _IO_setb instead of having _IO_setb and _IO_wsetb,
|> for example.
The wide stream stuff isn't actually that big. I was only able to reduce
the size by about 8.3K by leaving out the wide stream support (see the
attached patch for how I did that). The rest from libio is mostly the
printf stuff that is pulled in by malloc.
A much bigger problem is the gconv stuff, which is indirectly referenced
in strtol via btowc. The biggest single object file that is included is
regex.o, which is referenced by gconv_db.c. I don't see a way to reduce
this.
Andreas.
next prev parent reply other threads:[~1999-08-19 5:24 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 [this message]
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
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=jezozoarhu.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=zack@bitmover.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.
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).