https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64482
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #1) > Currently, user code that wants to support -fno-exceptions needs to provide > its own similar workarounds. That can be done by checking the > __cpp_exceptions feature-test macro (or __EXCEPTIONS for older releases). There is an argument for providing a feature in gcc when enough users are likely to use it, so they don't have to reinvent a triangular wheel. > IMHO it doesn't really make sense to expect to use 'throw' when exceptions > are disabled. You may want to use a third-party library that only uses throw for error reporting, where you are fine with aborting. IMHO, a way to automatically turn throw into abort/terminate would be a nice complement for -fno-exceptions (it can be a separate option, that doesn't really matter).
