Re: RFC: C++ PATCH to stop emitting code for throw() by default

[Jason Merrill <jason at redhat dot com>]

On 03/22/2010 01:01 PM, Mark Mitchell wrote:
> I recognize that we're talking about an intentionally non-conformant
> mode here; the EH equivalent of -ffast-math or some such.  Are you
> proposing that this be the default?

Yes.

> Also, how do we know that emitting nothing will result in a call to
> terminate?  Perhaps our caller has an exception handler that will catch
> this exception?

Because the function can't throw, no unwind information is emitted for 
calls to the function, so the unwinder can't unwind through the call and 
calls terminate.

Jason