public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: guerby@acm.org
Cc: gcc@gcc.gnu.org
Subject: Re: The bloat sweepstakes...
Date: Sun, 07 Oct 2001 11:26:00 -0000	[thread overview]
Message-ID: <20011007112616.O9432@codesourcery.com> (raw)
In-Reply-To: <200110071744.f97Hi3f16220@ulmo.localdomain>

On Sun, Oct 07, 2001 at 07:44:03PM +0200, guerby@acm.org wrote:
> > 1857.3  264.9   13.2   2321.9   4457.2  gnat1
> 
> I'm curious as from where this big BSS is coming from and I'm
> surprised BSS size is adding up into the final executable size, do I
> miss something (BSS does not need to be present in the executable
> since it's for unitialized data, right)?

BSS does not take up space in the on-disk file, but it does contribute
to the in-memory footprint of the compiler, so it seemed relevant.

Hmm... nm --size-sort suggests that most of it is lib__util__info_buffer,
weighing in at just over 2MB.  I think this is for dumping .ali files;
it's not clear to me why it is not using Text_IO.

zw

  reply	other threads:[~2001-10-07 11:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 10:25 Zack Weinberg
2001-10-07 10:44 ` guerby
2001-10-07 11:26   ` Zack Weinberg [this message]
2001-10-07 11:44     ` guerby
2001-10-07 12:43       ` Zack Weinberg
2001-10-07 14:42         ` guerby
2001-10-09 23:24 ` Fergus Henderson
2001-10-10 15:09   ` Zack Weinberg
2001-10-10 23:03     ` Fergus Henderson
2001-10-10 23:46       ` Zack Weinberg
2001-10-19  9:43     ` law
2001-10-22  0:39       ` Zack Weinberg
2001-10-22  8:28         ` law
2001-10-22 15:01           ` Richard Henderson
2001-10-07 15:16 dewar
2001-10-08  9:59 ` Zack Weinberg
2001-10-07 15:21 dewar
2001-10-07 15:24 dewar
2001-10-08 10:01 dewar
2001-10-08 10:03 dewar
2001-10-08 10:07 dewar
2001-10-08 11:04 ` 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=20011007112616.O9432@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.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).