17 Language support library [support]

Headers <csetjmp> (nonlocal jumps), <csignal> (signal handling), <cstdarg> (variable arguments), and <cstdlib> (runtime environment getenv, system), provide further compatibility with C code.

Calls to the function getenv ([cstdlib.syn]) shall not introduce a data race ([res.on.data.races]) provided that nothing modifies the environment.

A call to the setlocale function may introduce a data race with other calls to the setlocale function or with calls to functions that are affected by the current C locale.

The implementation shall behave as if no library function other than locale​::​global calls the setlocale function.

The contents of the header <cstdarg> are the same as the C standard library header <stdarg.h>, with the following changes: The restrictions that ISO C places on the second parameter to the va_­start macro in header <stdarg.h> are different in this document.

The parameter parmN is the rightmost parameter in the variable parameter list of the function definition (the one just before the ...).221

If the parameter parmN is a pack expansion ([temp.variadic]) or an entity resulting from a lambda capture ([expr.prim.lambda]), the program is ill-formed, no diagnostic required.

If the parameter parmN is of a reference type, or of a type that is not compatible with the type that results when passing an argument for which there is no parameter, the behavior is undefined.

See also: ISO C 7.16.1.1

The contents of the header <csetjmp> are the same as the C standard library header <setjmp.h>.

The function signature longjmp(jmp_­buf jbuf, int val) has more restricted behavior in this document.

A setjmp/longjmp call pair has undefined behavior if replacing the setjmp and longjmp by catch and throw would invoke any non-trivial destructors for any objects with automatic storage duration.

A call to setjmp or longjmp has undefined behavior if invoked in a suspension context of a coroutine ([expr.await]).

See also: ISO C 7.13

The contents of the header <csignal> are the same as the C standard library header <signal.h>.

A call to the function signal synchronizes with any resulting invocation of the signal handler so installed.

A plain lock-free atomic operation is an invocation of a function f from [atomics], such that:

• (2.1)
  f is the function atomic_­is_­lock_­free(), or
• (2.2)
  f is the member function is_­lock_­free(), or
• (2.3)
  f is a non-static member function invoked on an object A, such that A.is_­lock_­free() yields true, or
• (2.4)
  f is a non-member function, and for every pointer-to-atomic argument A passed to f, atomic_­is_­lock_­free(A) yields true.

An evaluation is signal-safe unless it includes one of the following:

• (3.1)
  a call to any standard library function, except for plain lock-free atomic operations and functions explicitly identified as signal-safe;
  [Note 1:

  This implicitly excludes the use of new and delete expressions that rely on a library-provided memory allocator.

  — end note]
• (3.2)
  an access to an object with thread storage duration;
• (3.3)
  a dynamic_­cast expression;
• (3.4)
  throwing of an exception;
• (3.5)
  control entering a try-block or function-try-block;
• (3.6)
  initialization of a variable with static storage duration requiring dynamic initialization ([basic.start.dynamic], [stmt.dcl])222; or
• (3.7)
  waiting for the completion of the initialization of a variable with static storage duration ([stmt.dcl]).

A signal handler invocation has undefined behavior if it includes an evaluation that is not signal-safe.

The function signal is signal-safe if it is invoked with the first argument equal to the signal number corresponding to the signal that caused the invocation of the handler.

See also: ISO C 7.14