Adding upstream version 6.7.upstream/6.7

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 7 insertions, 8 deletions

diff --git a/man3/pthread_exit.3 b/man3/pthread_exit.3
index 4f317a9..edd6f90 100644
--- a/man3/pthread_exit.3
+++ b/man3/pthread_exit.3
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH pthread_exit 3 2023-07-20 "Linux man-pages 6.05.01"
+.TH pthread_exit 3 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 pthread_exit \- terminate calling thread
 .SH LIBRARY
@@ -13,7 +13,7 @@ POSIX threads library
 .SH SYNOPSIS
 .nf
 .B #include <pthread.h>
-.PP
+.P
 .BI "[[noreturn]] void pthread_exit(void *" retval );
 .fi
 .SH DESCRIPTION
@@ -24,7 +24,7 @@ function terminates the calling thread and returns a value via
 that (if the thread is joinable)
 is available to another thread in the same process that calls
 .BR pthread_join (3).
-.PP
+.P
 Any clean-up handlers established by
 .BR pthread_cleanup_push (3)
 that have not yet been popped,
@@ -34,14 +34,14 @@ If the thread has any thread-specific data, then,
 after the clean-up handlers have been executed,
 the corresponding destructor functions are called,
 in an unspecified order.
-.PP
+.P
 When a thread terminates,
 process-shared resources (e.g., mutexes, condition variables,
 semaphores, and file descriptors) are not released,
 and functions registered using
 .BR atexit (3)
 are not called.
-.PP
+.P
 After the last thread in a process terminates,
 the process terminates as by calling
 .BR exit (3)
@@ -68,7 +68,6 @@ T{
 .BR pthread_exit ()
 T}	Thread safety	MT-Safe
 .TE
-.sp 1
 .SH STANDARDS
 POSIX.1-2008.
 .SH HISTORY
@@ -78,13 +77,13 @@ Performing a return from the start function of any thread other
 than the main thread results in an implicit call to
 .BR pthread_exit (),
 using the function's return value as the thread's exit status.
-.PP
+.P
 To allow other threads to continue execution,
 the main thread should terminate by calling
 .BR pthread_exit ()
 rather than
 .BR exit (3).
-.PP
+.P
 The value pointed to by
 .I retval
 should not be located on the calling thread's stack,