diff options
Diffstat (limited to 'man7/attributes.7')
| -rw-r--r-- | man7/attributes.7 | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/man7/attributes.7 b/man7/attributes.7 index 3d91b7b19f..d53252bf1a 100644 --- a/man7/attributes.7 +++ b/man7/attributes.7 @@ -98,7 +98,7 @@ safe for inlining. .\" but does document which functions are presently AC-Safe. .\" This documentation is provided for use .\" by the GNU C Library developers. - +.\" .\" Just like signal handlers, cancellation cleanup routines must configure .\" the floating point environment they require. .\" The routines cannot assume a floating point environment, @@ -345,7 +345,7 @@ Calling such a function at least once in single-threaded mode removes this specific cause for the function to be regarded as MT-Unsafe. If no other cause for that remains, the function can then be safely called after other threads are started. - +.\" .\" Functions marked with .\" .I init .\" as an AS-Unsafe or AC-Unsafe feature use the GNU C Library internal @@ -386,7 +386,7 @@ In some cases, the objects are passed to the functions by users; in others, they are used by the functions to return values to users; in others, they are not even exposed to users. - +.\" .\" We consider access to objects passed as (indirect) arguments to .\" functions to be data race free. .\" The assurance of data race free objects @@ -563,7 +563,7 @@ Holding a non-recursive mutex while calling all functions that use the same temporary signal; blocking that signal before the call and resetting its handler afterwards is recommended. - +.\" .\" There is no safe way to guarantee the original signal handler is .\" restored in case of asynchronous cancellation, .\" therefore so-marked functions are also AC-Unsafe. @@ -609,7 +609,7 @@ is a file descriptor for the controlling terminal. The caller may use a single mutex for simplicity, or use one mutex per terminal, even if referenced by different file descriptors. - +.\" .\" Functions marked with .\" .I term .\" as an AC-Safety issue are supposed to @@ -656,7 +656,6 @@ are running or asynchronous signals are enabled, and so the locale can be considered effectively constant in these contexts, which makes the former safe. - .\" Should the locking strategy suggested under @code{const} be used, .\" failure to guard locale uses is not as fatal as data races in .\" general: unguarded uses will @emph{not} follow dangling pointers or |