catch(...) and forced unwind

Richard Henderson rth@redhat.com
Mon Dec 15 22:54:00 GMT 2003


I'd just like to add that yet another reason to go with 
explicit rethrows instead of implicit rethrows is that
the compiler expects that

	catch (...) { }

consumes all exceptions, and so will DCE EH cleanups for
objects in outer scopes of the same function.  Disabling
this optimization is almost certainly a bad idea.


r~



More information about the Gcc mailing list