Re: Mark va_start as nothrow

[Mark Mitchell <mark at codesourcery dot com>]

Richard Guenther wrote:

>> But, to return to the core issue, I think that GCC's internal model of
>> builtin functions, when compiling with -fnon-call-exceptions, ought to
>> be that any external functions might raise such exceptions.

>> The empty exception specification for builtins is an optimization, but
>> with -fnon-call-exceptions, it doesn't sound like a safe optimization.

> I agree.  I guess the C++ standard doesn't specify what throw() means
> for non-call-exceptions?

Correct.  In ISO C++, there are no such things; you can only throw an
exception with an explicit "throw".  And, you explicitly cannot rely on
throwing exceptions out of signal handlers in portable code.

> Of course this is all a pre-existing problem and worth a bugzilla.

Indeed.  Have you already created one?  If not, I can do so.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713