On 10/23/20 7:46 AM, Jonathan Wakely wrote:
I think this test is intended to check this property of the C++
standard:

"If a destructor directly invoked by stack unwinding exits via an
exception, std::terminate is invoked." [except.throw]

Since C++11 any exception escaping a destructor will call
std::terminate, so the test would terminate even if the unwinding
behaviour was wrong.

Give the destructor a potentially-throwing exception specification,
so that we know that terminate was called for the right reason.

gcc/testsuite/ChangeLog:

        * g++.dg/compat/eh/filter2_y.C: Add noexcept(false) to
        destructor.


Tested powerpc64le-linux. OK for trunk?

ok


--
Nathan Sidwell

Reply via email to