News for hackers. Stuff that matters.

A comment on Investigating the Performance Overhead of C++ Exceptions. Parent comment

Re:Investigating the Performance Overhead of C++ Exceptions by cmrdporcupine on Tuesday February 11, 2020 @05:00PM (#22303377)
I believe the exception ban at Google these days is justified more on the grounds that integrating with existing code would be problematic, rather than on performance grounds. I seem to remember reading something to that effect.
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by billti on Tuesday February 11, 2020 @06:59PM (#22304318)
Their coding guidelines on the topic lay out the pros/cons and ultimate reasoning pretty well: https://google.github.io/styleguide/cppguide.html#Exceptions
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by thedance on Tuesday February 11, 2020 @07:57PM (#22304695)
That may be the explanation they've settled on but there are build artifacts at that company which would be impossible to link without -fno-exceptions, so there are also practical problems.
[ Parent | on HN ]
Re:Investigating the Performance Overhead of C++ Exceptions by ncmncm on Wednesday February 12, 2020 @10:58AM (#22309852)
This is correct. Google have many, many million lines of casually exception-unsafe code they cannot afford to fix, so any rationalization is only that. The choice is off the table.
[ Parent | on HN ]