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]

Re: -fno-exceptions and bad_alloc

To: jason at cygnus dot com (Jason Merrill)
Subject: Re: -fno-exceptions and bad_alloc
From: Andi Kleen <ak at muc dot de>
Date: 28 Sep 1999 12:32:30 +0200
cc: egcs at egcs dot cygnus dot com
References: <002701bf0948$0c20ba70$0301a8c0@DAGORLAD> <u9k8pbvo7z.fsf@yorick.cygnus.com>

jason@cygnus.com (Jason Merrill) writes:

> >>>>> Thomas van Gulick <list@utumno.student.utwente.nl> writes:
> 
>  > When using -fno-exceptions I still get bad_alloc exceptions
>  > thrown at me when the new operator fails. I also tried the
>  > fno-check-new flag to no avail.
>  > Is there any way to really really turn off exception handling
>  > and throwing?
> 
> Use new (nothrow).

Shouldn't this be the default for new when -fno-exceptions is enabled?


-Andi
-- 
This is like TV. I don't like TV.

References:
- -fno-exceptions and bad_alloc
  - From: Thomas van Gulick
- Re: -fno-exceptions and bad_alloc
  - From: Jason Merrill

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