https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372
--- Comment #11 from David Crocker <dcrocker at eschertech dot com> --- I've been bitten by this several times. In the absence of support for this type of checking in GCC I added exception checking to our own homebrew static analysis tool. It's already detected three situations in which invalid user input would cause termination of our application instead of an error message, due to a function throwing an exception when it was called from another function that was declared noexcept. I think removing more detailed exception specifications from C++ was a big mistake. I can understand that in many applications they were not needed; however in mission critical real-time applications that use exceptions in very limited ways, such as the one we write, it's vital to know that any exception thrown will be caught and handled, not cause termination.
