[PATCH] libstdc++: Fix exceptions being generated when compiling with -fno-exceptions

Jonathan Wakely jwakely.gcc@gmail.com
Tue Apr 14 19:27:00 GMT 2015


On 14 April 2015 at 16:17, Federico Lenarduzzi wrote:
> When the libstdc++ is compiled, the compiler sets the std::terminate_handler function with __verbose_terminate_handler() or std::abort() depending on _GLIBCXX_HOSTED && _GLIBCXX_VERBOSE being true or false.
>
> However, even if we compile with -fno-exceptions, the compiler will use __verbose_terminate_handler(), which uses exceptions. Therefore, the library is not fully exception-free.

I guess this makes sense, but you can just build with
--disable-libstdcxx-verbose to have the same effect.

> It also makes std::uncaught_exception() throw() return false if __EXCEPTIONS is not defined.

This part seems like a good idea, but we'll also need to do it to the
new uncaught_exceptions() function about to be added, so let's wait
until that in committed first (which will be shortly after the 5.1
release).

The checks should use __cpp_exceptions not __EXCEPTIONS, see the current trunk.



More information about the Libstdc++ mailing list