Steven Watanabe — Tue, 08 Jun 2010 01:24:24 GMT

Do you have a patch? Adding BOOST_ATTRIBUTE_NORETURN gives this warning instead:

boost/exception/detail/exception_ptr.hpp: In function 'void boost::rethrow_exception(const boost::exception_ptr&)':
boost/exception/detail/exception_ptr.hpp:391: warning: 'noreturn' function does return

I can't seem to get rid of this. Adding BOOST_ATTRIBUTE_NORETURN to clone_base::rethrow doesn't help.

Tue, 08 Jun 2010 16:06:33 GMT

No, I didn't make a patch as simple addition of BOOST_ATTRIBUTE_NORETURN to rethrow_exception was all was thinking of. That worked for me with msvc8 and didn't produce any warnings with /W4. After seeing your comment I tried the same with gcc 4.4.0 and indeed it gave me the same "'noreturn' function does return" warning. What is most annoying to me is that gcc gives such warnings even though there is a #pragma GCC system_header at the top of the header file. So I then tried adding a throw "convince the compiler this function doesn't return"; line after p->rethrow(); in rethrow_exception(), which made that warning to go away. With both BOOST_ATTRIBUTE_NORETURN and a dummy throw statement present, both msvc and gcc happily compile code without warnings they were previously complaining about. However I am not sure if that is an acceptable solution. Or maybe add BOOST_ATTRIBUTE_NORETURN only for msvc as the problem is more severe with msvc than with gcc? I don't know.

To be explicit, here's why I think this is more a problem with msvc than gcc. The following code

int f( boost::exception_ptr p )
{
   boost::rethrow_exception( p );
}

is rejected by msvc with an error saying that f must return a value, whereas gcc merely gives a "control reaches end of non-void function" warning.

Thanks for looking into this,

status changed; resolution set

Emil Dotchevski — Sat, 12 Feb 2011 00:08:42 GMT

status new → closed
resolution → fixed

Boost C++ Libraries: Ticket #4282: Please add BOOST_ATTRIBUTE_NORETURN to rethrow_exception()

status changed; resolution set