From: Brian Glendenning <bglenden@aoc.nrao.edu>
To: Joern Rennecke <amylaar@cygnus.co.uk>
Cc: egcs@cygnus.com
Subject: Re: egcs 1.0.2 c++ .o size
Date: Fri, 27 Mar 1998 15:18:00 -0000 [thread overview]
Message-ID: <351A7B62.E667595B@aoc.nrao.edu> (raw)
In-Reply-To: <199803261534.PAA09782@phal.cygnus.co.uk>
> > Our binaries are already embarrasingly large - I'd hate to have them
> > become 50% more so!
>
> Since 2.7.2 , exception handling has been added. You can use the
> -fno-exceptions option to avoid the overhead of exception handling.
OK thanks - indeed that gets our objects down to about the same size (still
about 5% larger).
Is the 50% size penalty going to continue into the future? We have an
exception emulation (setjmp/longjmp, keeping classes derived from "Cleanup"
in a list) that we'd dearly like to get rid of, but 50% is a fairly steep
price to pay.
Brian
next prev parent reply other threads:[~1998-03-27 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-24 16:25 Brian Glendenning
1998-03-27 15:18 ` Joern Rennecke
1998-03-27 15:18 ` Brian Glendenning [this message]
1998-03-31 0:46 ` Jim Wilson
1998-03-27 15:18 ` Jeffrey A Law
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=351A7B62.E667595B@aoc.nrao.edu \
--to=bglenden@aoc.nrao.edu \
--cc=amylaar@cygnus.co.uk \
--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).