From: mrs@wrs.com (Mike Stump)
To: amylaar@cygnus.co.uk, bglenden@aoc.nrao.edu
Cc: egcs@cygnus.com
Subject: Re: egcs 1.0.2 c++ .o size
Date: Mon, 30 Mar 1998 16:18:00 -0000 [thread overview]
Message-ID: <199803302119.NAA07654@kankakee.wrs.com> (raw)
> Date: Thu, 26 Mar 1998 08:59:30 -0700
> From: Brian Glendenning <bglenden@aoc.nrao.edu>
> Is the 50% size penalty going to continue into the future?
Yes, unless someone fixes it. We all would like to see this number
smaller, but until someone ponies up the work to reduce it...
> 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.
Use -fsjlj-exceptions, and compare against your application without
your extra EH emulation code in the object. I'm thinking that you
should come pretty close then.
next reply other threads:[~1998-03-30 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-30 16:18 Mike Stump [this message]
1998-04-01 13:41 ` Brian Glendenning
-- strict thread matches above, loose matches on Subject: below --
1998-03-26 18:14 Mike Stump
1998-03-24 16:25 Brian Glendenning
1998-03-27 15:18 ` Joern Rennecke
1998-03-27 15:18 ` Brian Glendenning
1998-03-31 0:46 ` Jim Wilson
1998-03-27 15:18 ` Jeffrey A Law
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=199803302119.NAA07654@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=amylaar@cygnus.co.uk \
--cc=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).