This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: "new" statement and -fno-exceptions

From: Paolo Carlini <pcarlini at suse dot de>
To: Mike Stump <mrs at apple dot com>
Cc: Paul Koning <pkoning at equallogic dot com>, gcc at gcc dot gnu dot org
Date: Tue, 05 Oct 2004 01:32:42 +0200
Subject: Re: "new" statement and -fno-exceptions
References: <16737.21023.734280.866426@gargle.gargle.HOWL> <0C983E7B-165B-11D9-8C12-003065A77310@apple.com>

Mike Stump wrote:

-fno-exceptions doesn't change code you call, only your code that you compile. In your case, you call a routine that throws, and it does; the solution is to stop calling routines that throw.

Right. However, recompiling libsupc++ with -fno-exceptions should do the trick, in principle... (not that I'm suggesting that ;)

Paolo.

References:
- "new" statement and -fno-exceptions
  - From: Paul Koning
- Re: "new" statement and -fno-exceptions
  - From: Mike Stump

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]