From: Marius Vollmer <mvo@zagadka.ping.de>
To: guile-gtk@sourceware.cygnus.com
Subject: Re: Towards guile-gtk 0.18
Date: Sun, 31 Oct 1999 05:14:00 -0000 [thread overview]
Message-ID: <87so2r97gz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3wvs412vq.fsf@savonarola.red-bean.com>
Jim Blandy <jimb@red-bean.com> writes:
> > I'm a bit worried about the size of gtk-glue.c, too.
>
> Some historical perspective: people used to make fun of the Mach
> microkernel because it wasn't very "micro" --- it was bigger than a
> BSD kernel on the same machine. And it didn't even have filesystems,
> networking stacks, and so on.
[ Yeah, I know. I'm just about to assess how difficult it would be to
port GNU Mach to Linux, that is, to use unmodified Linux code for
the machine specific parts of Mach. I want to run the Hurd on my
iMac. ]
> It turns out that a full half of the executable was due to
> automatically generated RPC stubs.
Yes. I have done some minimal survey and it turnes out that a
libguilegtk without any actual stubs in it has this size
% size .libs/libguilegtk-1.3.so.0.0.0
text data bss dec hex filename
36719 1324 84 38127 94ef .libs/libguilegtk-1.3.so.0.0.0
while the regular one has
% size /usr/local/lib/libguilegtk-1.3.so.0.0.0
text data bss dec hex filename
295734 36180 84 331998 510de libguilegtk-1.3.so.0.0.0
This might not be very relevant because a glue library is supposed to
contain mostly glue, but it shows that reducing the glue portion of
libguilegtk would have siginificant effects.
- Marius
next prev parent reply other threads:[~1999-10-31 5:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-24 13:14 Ariel Rios
1999-10-25 7:46 ` Miroslav Silovic
1999-10-25 10:55 ` Marius Vollmer
1999-10-25 14:45 ` Miroslav Silovic
1999-10-30 23:05 ` Jim Blandy
1999-10-31 4:34 ` Miroslav Silovic
1999-10-31 5:14 ` Marius Vollmer [this message]
1999-10-31 9:54 ` Keith Wright
1999-11-01 6:37 ` Jim Blandy
1999-11-02 21:42 ` Keith Wright
1999-11-13 7:42 ` Towards guile-gtk x.xx Daniel Skarda
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=87so2r97gz.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-gtk@sourceware.cygnus.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).