In what ways do C++ exceptions slow down code when there are no exceptions thown?

by

There is a cost associated with exception handling on some platforms and with some compilers.

Namely, Visual Studio, when building a 32-bit target, will register a handler in every function that has local variables with non-trivial destructor. Basically, it sets up a try/finally handler.

The other technique, employed by gcc and Visual Studio targeting 64-bits, only incurs overhead when an exception is thrown (the technique involves traversing the call stack and table lookup). In cases where exceptions are rarely thrown, this can actually lead to a more efficient code, as error codes don’t have to be processed.

More Related Contents:

  1. Possibilities to quit a function
  2. If you shouldn’t throw exceptions in a destructor, how do you handle errors in it?
  3. Does C++ support ‘finally’ blocks? (And what’s this ‘RAII’ I keep hearing about?)
  4. C++ display stack trace on exception
  5. Why will std::sort crash if the comparison function is not as operator
  6. Throwing exceptions from constructors
  7. Can placement new for arrays be used in a portable way?
  8. Why should exceptions be used conservatively?
  9. Should I use an exception specifier in C++?
  10. GDB complaining about missing raise.c
  11. Why doesn’t C++ use std::nested_exception to allow throwing from destructor?
  12. Throw keyword in function’s signature
  13. How do exceptions work (behind the scenes) in c++
  14. Who deletes the memory allocated during a “new” operation which has exception in constructor?
  15. Difference between C++03 throw() specifier C++11 noexcept
  16. C++: Safe to use longjmp and setjmp?
  17. C++ – Arguments for Exceptions over Return Codes
  18. Windows/C++: Is it possible to find the line of code where exception was thrown having “Exception Offset”
  19. What should I know about Structured Exceptions (SEH) in C++?
  20. Why are C++ STL iostreams not “exception friendly”?
  21. boost thread throwing exception “thread_resource_error: resource temporarily unavailable”
  22. Why destructor is not called on exception?
  23. Should I inherit from std::exception?
  24. How much overhead is there in calling a function in C++?
  25. Does throw inside a catch ellipsis (…) rethrow the original error in C++?
  26. Under what circumstances are C++ destructors not going to be called?
  27. Difference between a C++ exception and Structured Exception
  28. Measuring exception handling overhead in C++
  29. Why is a segmentation fault not recoverable?
  30. Throwing C++ exceptions across DLL boundaries

Leave a Comment