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

Jason Merrill jason@redhat.com
Mon Mar 22 19:13:00 GMT 2010


On 03/22/2010 01:26 PM, Mark Mitchell wrote:
>> 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.

Actually, I was wrong about this, just omitting the EH spec code can 
lead to an exception escaping.  Never mind...

Jason



More information about the Gcc-patches mailing list