objects of lock-free std::atomic types (since C++11).objects of type volatile std:: sig_atomic_t.On entry to the signal handler, the state of the floating-point environment and the values of all objects is unspecified, except for
If the signal handler is called as a result of std::abort or std::raise (synchronous signal), the behavior is undefined if the signal handler calls std::raise. If the user defined function returns when handling SIGFPE, SIGILL, SIGSEGV or any other implementation-defined signal specifying a computational exception, the behavior is undefined. waits for completion of initialization of any variable with static storage duration due to another thread concurrently initializing it.initialization of a static variable that performs dynamic non-local initialization (including delayed until first ODR-use).entry to a try block, including function- try-block.access to an object with thread storage duration.std::forward, std::move, std::move_if_noexcept.The member functions of std::initializer_list and the std::initializer_list overloads of std::begin and std::end.member functions of std::numeric_limits.std :: signal with the first argument being the number of the signal currently handled (signal handler can re-register itself, but not other signals).The functions std::atomic_is_lock_free and std::atomic::is_lock_free are signal-safe for any atomic type. members functions of std::atomic and non-member functions from if the atomic type they operate on is lock-free.call to any library function, except the following signal-safe functions (note, in particular, dynamic allocation is not signal-safe):.
The behavior is undefined if any signal handler performs any of the following:
0 kommentar(er)
