public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: slouken@devolution.com
Cc: egcs@egcs.cygnus.com, highlander@lokigames.com
Subject: Re: Large code size?
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <199903250725.IAA00726@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990331234600.1hEdeyYEEIgafUGn0g8Fx4Y0neWPCdZYLfr_JsdUXWc@z> (raw)
In-Reply-To: <E10PwfK-0001bs-00@roboto.devolution.com>

> Also, when linking with either cc1 or cc1plus, and specifying
> -fno-exceptions, the exception.o object from libgcc.a is still
> linked in.
> 
> Ideas?

If you use ::operator new, it might throw exceptions, so you get some
exception routines in. Also, it always has to provide the frame
unwinding code for the shared library, regardless of whether some
object files never throw exceptions and don't support unwinding.

Regards,
Martin

  parent reply	other threads:[~1999-03-31 23:46 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-24 15:05 Sam Lantinga
     [not found] ` < E10PwfK-0001bs-00@roboto.devolution.com >
1999-03-24 23:26   ` Martin v. Loewis
1999-03-31 23:46     ` Martin v. Loewis
1999-03-24 23:35   ` Martin v. Loewis [this message]
1999-03-31 23:46     ` Martin v. Loewis
1999-03-31 23:46 ` Sam Lantinga
  -- strict thread matches above, loose matches on Subject: below --
1999-03-25  9:49 Sam Lantinga
     [not found] ` < E10QEFo-0002NA-00@roboto.devolution.com >
1999-03-25 10:14   ` H.J. Lu
1999-03-31 23:46     ` H.J. Lu
1999-03-31 23:46 ` Sam Lantinga
1999-03-25  9:48 Sam Lantinga
1999-03-25 11:24 ` Jason Merrill
1999-03-31 23:46   ` Jason Merrill
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 17:57 N8TM
1999-03-31 23:46 ` N8TM
1999-03-24 16:47 Sam Lantinga
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 16:34 Mike Stump
1999-03-31 23:46 ` Mike Stump
1999-03-24 16:28 Sam Lantinga
     [not found] ` < E10Py0p-0001gL-00@roboto.devolution.com >
1999-03-24 16:45   ` Joe Buck
1999-03-31 23:46     ` Joe Buck
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 15:42 Sam Lantinga
     [not found] ` < E10PxHr-0001fO-00@roboto.devolution.com >
1999-03-24 15:54   ` Joe Buck
     [not found]     ` < 199903242353.PAA02719@atrus.synopsys.com >
1999-03-24 23:22       ` Martin v. Loewis
1999-03-31 23:46         ` Martin v. Loewis
1999-03-31 23:46     ` Joe Buck
1999-03-24 17:07   ` H.J. Lu
     [not found]     ` < m10PycJ-000ErMC@ocean.lucon.org >
1999-03-25  5:04       ` Nick Ing-Simmons
1999-03-31 23:46         ` Nick Ing-Simmons
1999-03-31 23:46     ` H.J. Lu
     [not found] ` <199903242353.PAA02719.cygnus.egcs@atrus.synopsys.com>
1999-03-25  1:08   ` Jason Merrill
1999-03-25  8:28     ` Andi Kleen
1999-03-31 23:46       ` Andi Kleen
     [not found]     ` < u9n212vswe.fsf@yorick.cygnus.com >
1999-03-25 14:35       ` Martin v. Loewis
1999-03-31 23:46         ` Martin v. Loewis
1999-03-31 23:46     ` Jason Merrill
1999-03-31 23:46 ` Sam Lantinga
     [not found] <E10PwA2-0001UN-00@roboto.devolution.com>
1999-03-24 14:42 ` Martin von Loewis
1999-03-24 14:49   ` Dima Volodin
1999-03-31 23:46     ` Dima Volodin
1999-03-31 23:46   ` Martin von Loewis
1999-03-24 13:52 Sam Lantinga
     [not found] ` < E10PvY5-0001NJ-00@roboto.devolution.com >
1999-03-24 14:10   ` Martin v. Loewis
1999-03-31 23:46     ` Martin v. Loewis
1999-03-24 15:18   ` H.J. Lu
1999-03-31 23:46     ` H.J. Lu
1999-03-31 23:46 ` Sam Lantinga
1999-03-24  9:38 Sam Lantinga
     [not found] ` < E10PrbT-0003Og-00@roboto.devolution.com >
1999-03-24 13:29   ` David B. Rees
1999-03-31 23:46     ` David B. Rees
1999-03-24 13:38   ` Martin v. Loewis
1999-03-31 23:46     ` Martin v. Loewis
1999-03-31 23:46 ` Sam Lantinga

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=199903250725.IAA00726@mira.isdn.cs.tu-berlin.de \
    --to=martin@mira.isdn.cs.tu-berlin.de \
    --cc=egcs@egcs.cygnus.com \
    --cc=highlander@lokigames.com \
    --cc=slouken@devolution.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).