Section 5.4 of the draft Technical Report on C++ Performance is entirely devoted to the overhead of exceptions.
More Related Contents:
- Why is my program slow when looping over exactly 8192 elements?
- Visual C++ equivalent of GCC’s __attribute__ ((__packed__))
- How do exceptions work (behind the scenes) in c++
- Difference in performance between MSVC and GCC for highly optimized matrix multplication code
- Inherit interfaces which share a method name
- C++: Safe to use longjmp and setjmp?
- Why does GCC generate 15-20% faster code if I optimize for size instead of speed?
- Will C++ exceptions safely propagate through C code?
- Linking to MSVC DLL from MinGW
- Exception Error c0000005 in VC++
- Why destructor is not called on exception?
- Layout of compiled objects
- Using bts assembly instruction with gcc compiler
- How do I temporarily disable a macro expansion in C/C++?
- Why is std::vector::operator[] 5 to 10 times faster than std::vector::at()?
- New (std::nothrow) vs. New within a try/catch block
- Virtual functions and performance – C++
- Trying to understand gcc option -fomit-frame-pointer
- How can I measure CPU time and wall clock time on both Linux/Windows?
- GCC STL bound checking
- Why are Python Programs often slower than the Equivalent Program Written in C or C++?
- What does the operation c=a+++b mean?
- Is using #pragma warning push/pop the right way to temporarily alter warning level?
- undefined reference to `__stack_chk_fail’
- A fast method to round a double to a 32-bit int explained
- SetJmp/LongJmp: Why is this throwing a segfault?
- Is accessing data in the heap faster than from the stack?
- C++20 constexpr vector and string not working
- throw new std::exception vs throw std::exception
- Should I still return const objects in C++11? [duplicate]