public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Glendenning <bglenden@aoc.nrao.edu>
To: egcs@cygnus.com
Subject: egcs 1.0.2 c++ .o size
Date: Tue, 24 Mar 1998 16:25:00 -0000	[thread overview]
Message-ID: <35184EE6.575F538E@aoc.nrao.edu> (raw)

We have a largish (wc -l *.cc *.h = 780k) set of libraries and
applications (primarily) written in C++. The code is fairly heavily
templated.

While trying egcs, I noticed that the .o files and resulting executables
are about 50% larger than their g++ 2.7.2 counterparts when compiled
optimized (-O2 in both cases) on solaris. Is this common, or is
something bad probably happening (e.g. inlines going static).  If
something bad is probably happening, what are the usual suspects?

Our binaries are already embarrasingly large - I'd hate to have them
become 50% more so!

Thanks! -

Brian

[The debug binaries are about 25% larger]



             reply	other threads:[~1998-03-24 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-24 16:25 Brian Glendenning [this message]
1998-03-27 15:18 ` Jeffrey A Law
1998-03-27 15:18 ` Joern Rennecke
1998-03-27 15:18   ` Brian Glendenning
1998-03-31  0:46     ` Jim Wilson
1998-03-26 18:14 Mike Stump
1998-03-30 16:18 Mike Stump
1998-04-01 13:41 ` Brian Glendenning

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=35184EE6.575F538E@aoc.nrao.edu \
    --to=bglenden@aoc.nrao.edu \
    --cc=egcs@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).