"PTHREAD_BARRIER_DESTROY"(P) manual page

From aaa4964a2277a1e265da4e7b91d5b1e3c3faa84e Mon Sep 17 00:00:00 2001 From: marha Date: Mon, 17 Jan 2011 18:27:35 +0000 Subject: cvs update pthreads --- pthreads/manual/ChangeLog | 128 +++---- pthreads/manual/pthread_barrier_init.html | 395 ++++++++++----------- pthreads/manual/pthread_barrier_wait.html | 326 +++++++++-------- pthreads/manual/pthread_setschedparam.html | 225 ++++++------ .../manual/pthread_win32_attach_detach_np.html | 148 ++++---- 5 files changed, 609 insertions(+), 613 deletions(-) (limited to 'pthreads/manual') diff --git a/pthreads/manual/ChangeLog b/pthreads/manual/ChangeLog index c07cdd702..3b7ab307b 100644 --- a/pthreads/manual/ChangeLog +++ b/pthreads/manual/ChangeLog @@ -1,62 +1,66 @@ -2005-05-06 Ross Johnson - - * PortabilityIssues.html: Was nonPortableIssues.html. - * index.html: Updated; add table of contents at top. - * *.html: Add Pthreads-win32 header info; add link back to the - index page 'index.html'. - -2005-05-06 Ross Johnson - - * index.html: New. - * nonPortableIssues.html: New. - * pthread_attr_init.html: New. - * pthread_attr_setstackaddr.html: New. - * pthread_attr_setstacksize.html: New. - * pthread_barrierattr_init.html: New. - * pthread_barrierattr_setpshared.html: New. - * pthread_barrier_init.html: New. - * pthread_barrier_wait.html: New. - * pthreadCancelableWait.html: New. - * pthread_cancel.html: New. - * pthread_cleanup_push.html: New. - * pthread_condattr_init.html: New. - * pthread_condattr_setpshared.html: New. - * pthread_cond_init.html: New. - * pthread_create.html: New. - * pthread_delay_np.html: New. - * pthread_detach.html: New. - * pthread_equal.html: New. - * pthread_exit.html: New. - * pthread_getw32threadhandle_np.html: New. - * pthread_join.html: New. - * pthread_key_create.html: New. - * pthread_kill.html: New. - * pthread_mutexattr_init.html: New. - * pthread_mutexattr_setpshared.html: New. - * pthread_mutex_init.html: New. - * pthread_num_processors_np.html: New. - * pthread_once.html: New. - * pthread_rwlockattr_init.html: New. - * pthread_rwlockattr_setpshared.html: New. - * pthread_rwlock_init.html: New. - * pthread_rwlock_rdlock.html: New. - * pthread_rwlock_timedrdlock.html: New. - * pthread_rwlock_timedwrlock.html: New. - * pthread_rwlock_unlock.html: New. - * pthread_rwlock_wrlock.html: New. - * pthread_self.html: New. - * pthread_setcancelstate.html: New. - * pthread_setcanceltype.html: New. - * pthread_setconcurrency.html: New. - * pthread_setschedparam.html: New. - * pthread_spin_init.html: New. - * pthread_spin_lock.html: New. - * pthread_spin_unlock.html: New. - * pthread_timechange_handler_np.html: New. - * pthread_win32_attach_detach_np.html: New. - * pthread_win32_test_features_np.html: New. - * sched_get_priority_max.html: New. - * sched_getscheduler.html: New. - * sched_setscheduler.html: New. - * sched_yield.html: New. - * sem_init.html: New. +2008-06-30 Ross Johnson + + pthread_setschedparam.html: Fix "see also" links. + +2005-05-06 Ross Johnson + + * PortabilityIssues.html: Was nonPortableIssues.html. + * index.html: Updated; add table of contents at top. + * *.html: Add Pthreads-win32 header info; add link back to the + index page 'index.html'. + +2005-05-06 Ross Johnson + + * index.html: New. + * nonPortableIssues.html: New. + * pthread_attr_init.html: New. + * pthread_attr_setstackaddr.html: New. + * pthread_attr_setstacksize.html: New. + * pthread_barrierattr_init.html: New. + * pthread_barrierattr_setpshared.html: New. + * pthread_barrier_init.html: New. + * pthread_barrier_wait.html: New. + * pthreadCancelableWait.html: New. + * pthread_cancel.html: New. + * pthread_cleanup_push.html: New. + * pthread_condattr_init.html: New. + * pthread_condattr_setpshared.html: New. + * pthread_cond_init.html: New. + * pthread_create.html: New. + * pthread_delay_np.html: New. + * pthread_detach.html: New. + * pthread_equal.html: New. + * pthread_exit.html: New. + * pthread_getw32threadhandle_np.html: New. + * pthread_join.html: New. + * pthread_key_create.html: New. + * pthread_kill.html: New. + * pthread_mutexattr_init.html: New. + * pthread_mutexattr_setpshared.html: New. + * pthread_mutex_init.html: New. + * pthread_num_processors_np.html: New. + * pthread_once.html: New. + * pthread_rwlockattr_init.html: New. + * pthread_rwlockattr_setpshared.html: New. + * pthread_rwlock_init.html: New. + * pthread_rwlock_rdlock.html: New. + * pthread_rwlock_timedrdlock.html: New. + * pthread_rwlock_timedwrlock.html: New. + * pthread_rwlock_unlock.html: New. + * pthread_rwlock_wrlock.html: New. + * pthread_self.html: New. + * pthread_setcancelstate.html: New. + * pthread_setcanceltype.html: New. + * pthread_setconcurrency.html: New. + * pthread_setschedparam.html: New. + * pthread_spin_init.html: New. + * pthread_spin_lock.html: New. + * pthread_spin_unlock.html: New. + * pthread_timechange_handler_np.html: New. + * pthread_win32_attach_detach_np.html: New. + * pthread_win32_test_features_np.html: New. + * sched_get_priority_max.html: New. + * sched_getscheduler.html: New. + * sched_setscheduler.html: New. + * sched_yield.html: New. + * sem_init.html: New. diff --git a/pthreads/manual/pthread_barrier_init.html b/pthreads/manual/pthread_barrier_init.html index 065c1296f..637630ea5 100644 --- a/pthreads/manual/pthread_barrier_init.html +++ b/pthreads/manual/pthread_barrier_init.html @@ -1,200 +1,197 @@ - - - - - "PTHREAD_BARRIER_DESTROY"(P) manual page - - - - - - - - -

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_barrier_destroy, pthread_barrier_init - destroy and -initialize a barrier object (ADVANCED REALTIME THREADS) -

Synopsis

#include <pthread.h> -

int pthread_barrier_destroy(pthread_barrier_t *barrier); -
int pthread_barrier_init(pthread_barrier_t *restrict barrier, -const pthread_barrierattr_t *restrict attr, unsigned -count); -

Description

The pthread_barrier_destroy function shall destroy the -barrier referenced by barrier and release any resources used -by the barrier. The effect of subsequent use of the barrier is -undefined until the barrier is reinitialized by another call to -pthread_barrier_init . An implementation may use this function -to set barrier to an invalid value. The results are undefined -if pthread_barrier_destroy is called when any thread is -blocked on the barrier, or if this function is called with an -uninitialized barrier. -

The pthread_barrier_init function shall allocate any -resources required to use the barrier referenced by barrier -and shall initialize the barrier with attributes referenced by attr. -If attr is NULL, the default barrier attributes shall be used; -the effect is the same as passing the address of a default barrier -attributes object. The results are undefined if pthread_barrier_init -is called when any thread is blocked on the barrier (that is, has not -returned from the pthread_barrier_wait(3) -call). The results are undefined if a barrier is used without first -being initialized. The results are undefined if pthread_barrier_init -is called specifying an already initialized barrier. -

The count argument specifies the number of threads that -must call pthread_barrier_wait(3) -before any of them successfully return from the call. The value -specified by count must be greater than zero. -

If the pthread_barrier_init function fails, the barrier -shall not be initialized and the contents of barrier are -undefined. -

Only the object referenced by barrier may be used for -performing synchronization. The result of referring to copies of that -object in calls to pthread_barrier_destroy or -pthread_barrier_wait(3) -is undefined.

Return Value

Upon successful completion, these functions shall return zero; -otherwise, an error number shall be returned to indicate the error. -

Errors

The pthread_barrier_destroy function may fail if: -

EBUSY -: - The implementation has detected an attempt to destroy a barrier - while it is in use (for example, while being used in a - pthread_barrier_wait(3) - call) by another thread. -
- EINVAL -: - The value specified by barrier is invalid. -

-The pthread_barrier_init function shall fail if: -

EAGAIN -: - The system lacks the necessary resources to initialize another - barrier. -
- EINVAL -: - The value specified by count is equal to zero. -
- ENOMEM -: - Insufficient memory exists to initialize the barrier. -

-The pthread_barrier_init function may fail if: -

EBUSY -: - The implementation has detected an attempt to reinitialize a barrier - while it is in use (for example, while being used in a - pthread_barrier_wait(3) - call) by another thread. -
- EINVAL -: - The value specified by attr is invalid. -

-These functions shall not return an error code of [EINTR]. -

The following sections are informative. -

Examples

None. -

Application Usage

The pthread_barrier_destroy and pthread_barrier_init -functions are part of the Barriers option and need not be provided on -all implementations. -

Pthreads-w32 defines _POSIX_BARRIERS to indicate -that these routines are implemented and may be used.

Rationale

None. -

Future Directions

None. -

Known Bugs

In - pthreads-win32, - pthread_barrier_wait(3) - may deadlock if the number of running threads able to wait on the - barrier object exceeds the value given as the count - parameter in pthread_barrier_init. -

-See Also

pthread_barrier_wait(3) -, the Base Definitions volume of IEEE Std 1003.1-2001, -<pthread.h> -

Copyright

Portions of this text are reprinted and reproduced in electronic -form from IEEE Std 1003.1, 2003 Edition, Standard for Information -Technology -- Portable Operating System Interface (POSIX), The Open -Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the -Institute of Electrical and Electronics Engineers, Inc and The Open -Group. In the event of any discrepancy between this version and the -original IEEE and The Open Group Standard, the original IEEE and The -Open Group Standard is the referee document. The original Standard -can be obtained online at http://www.opengroup.org/unix/online.html -. -

Modified by Ross Johnson for use with Pthreads-w32.

Table of Contents

Name -
-
Synopsis -
-
Description -
-
Return - Value -
-
Errors -
-
Examples -
-
Application - Usage -
-
Rationale -
-
Future - Directions -
-
Known - Bugs -
-
See - Also -
-
Copyright -
-

- + + + + + "PTHREAD_BARRIER_DESTROY"(P) manual page + + + + + + + + +

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_barrier_destroy, pthread_barrier_init - destroy and +initialize a barrier object (ADVANCED REALTIME THREADS) +

Synopsis

#include <pthread.h> +

int pthread_barrier_destroy(pthread_barrier_t *barrier); +
int pthread_barrier_init(pthread_barrier_t *restrict barrier, +const pthread_barrierattr_t *restrict attr, unsigned +count); +

Description

The pthread_barrier_destroy function shall destroy the +barrier referenced by barrier and release any resources used +by the barrier. The effect of subsequent use of the barrier is +undefined until the barrier is reinitialized by another call to +pthread_barrier_init . An implementation may use this function +to set barrier to an invalid value. An error code is returned if pthread_barrier_destroy is called when any thread is +blocked on the barrier, or if this function is called with an +uninitialized barrier. +

The pthread_barrier_init function shall allocate any +resources required to use the barrier referenced by barrier +and shall initialize the barrier with attributes referenced by attr. +If attr is NULL, the default barrier attributes shall be used; +the effect is the same as passing the address of a default barrier +attributes object. The results are undefined if pthread_barrier_init +is called when any thread is blocked on the barrier (that is, has not +returned from the pthread_barrier_wait(3) +call). The results are undefined if a barrier is used without first +being initialized. The results are undefined if pthread_barrier_init +is called specifying an already initialized barrier. +

The count argument specifies the number of threads that +must call pthread_barrier_wait(3) +before any of them successfully return from the call. The value +specified by count must be greater than zero. +

If the pthread_barrier_init function fails, the barrier +shall not be initialized and the contents of barrier are +undefined. +

Only the object referenced by barrier may be used for +performing synchronization. The result of referring to copies of that +object in calls to pthread_barrier_destroy or +pthread_barrier_wait(3) +is undefined.

Return Value

Upon successful completion, these functions shall return zero; +otherwise, an error number shall be returned to indicate the error. +

Errors

The pthread_barrier_destroy function may fail if: +

EBUSY +: + The implementation has detected an attempt to destroy a barrier + while it is in use (for example, while being used in a + pthread_barrier_wait(3) + call) by another thread. +
+ EINVAL +: + The value specified by barrier is invalid. +

+The pthread_barrier_init function shall fail if: +

EAGAIN +: + The system lacks the necessary resources to initialize another + barrier. +
+ EINVAL +: + The value specified by count is equal to zero. +
+ ENOMEM +: + Insufficient memory exists to initialize the barrier. +

+The pthread_barrier_init function may fail if: +

EBUSY +: + The implementation has detected an attempt to reinitialize a barrier + while it is in use (for example, while being used in a + pthread_barrier_wait(3) + call) by another thread. +
+ EINVAL +: + The value specified by attr is invalid. +

+These functions shall not return an error code of [EINTR]. +

The following sections are informative. +

Examples

None. +

Application Usage

The pthread_barrier_destroy and pthread_barrier_init +functions are part of the Barriers option and need not be provided on +all implementations. +

Pthreads-w32 defines _POSIX_BARRIERS to indicate +that these routines are implemented and may be used.

Rationale

None. +

Future Directions

None. +

Known Bugs

In + pthreads-win32, + the behaviour of threads which enter pthread_barrier_wait(3) + while the barrier is being destroyed is undefined. +

+See Also

pthread_barrier_wait(3) +, the Base Definitions volume of IEEE Std 1003.1-2001, +<pthread.h> +

Copyright

Portions of this text are reprinted and reproduced in electronic +form from IEEE Std 1003.1, 2003 Edition, Standard for Information +Technology -- Portable Operating System Interface (POSIX), The Open +Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the +Institute of Electrical and Electronics Engineers, Inc and The Open +Group. In the event of any discrepancy between this version and the +original IEEE and The Open Group Standard, the original IEEE and The +Open Group Standard is the referee document. The original Standard +can be obtained online at http://www.opengroup.org/unix/online.html +. +

Modified by Ross Johnson for use with Pthreads-w32.

Table of Contents

Name +
+
Synopsis +
+
Description +
+
Return + Value +
+
Errors +
+
Examples +
+
Application + Usage +
+
Rationale +
+
Future + Directions +
+
Known + Bugs +
+
See + Also +
+
Copyright +
+

+ \ No newline at end of file diff --git a/pthreads/manual/pthread_barrier_wait.html b/pthreads/manual/pthread_barrier_wait.html index 693d8bd15..e8eb2d16c 100644 --- a/pthreads/manual/pthread_barrier_wait.html +++ b/pthreads/manual/pthread_barrier_wait.html @@ -1,167 +1,161 @@ - - - - - "PTHREAD_BARRIER_WAIT"(P) manual page - - - - - - - - -

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_barrier_wait - synchronize at a barrier (ADVANCED -REALTIME THREADS) -

Synopsis

#include <pthread.h> -

int pthread_barrier_wait(pthread_barrier_t *barrier); - -

Description

The pthread_barrier_wait function shall synchronize -participating threads at the barrier referenced by barrier. -The calling thread shall block until the required number of threads -have called pthread_barrier_wait specifying the barrier. -

When the required number of threads have called -pthread_barrier_wait specifying the barrier, the constant -PTHREAD_BARRIER_SERIAL_THREAD shall be returned to one -unspecified thread and zero shall be returned to each of the -remaining threads. At this point, the barrier shall be reset to the -state it had as a result of the most recent pthread_barrier_init(3) -function that referenced it. -

The constant PTHREAD_BARRIER_SERIAL_THREAD is defined in -<pthread.h> and its value shall be distinct from any -other value returned by pthread_barrier_wait . -

The results are undefined if this function is called with an -uninitialized barrier. -

If a signal is delivered to a thread blocked on a barrier, upon -return from the signal handler the thread shall resume waiting at the -barrier if the barrier wait has not completed (that is, if the -required number of threads have not arrived at the barrier during the -execution of the signal handler); otherwise, the thread shall -continue as normal from the completed barrier wait. Until the thread -in the signal handler returns from it, it is unspecified whether -other threads may proceed past the barrier once they have all reached -it. -

A thread that has blocked on a barrier shall not prevent any -unblocked thread that is eligible to use the same processing -resources from eventually making forward progress in its execution. -Eligibility for processing resources shall be determined by the -scheduling policy. -

Return Value

Upon successful completion, the pthread_barrier_wait -function shall return PTHREAD_BARRIER_SERIAL_THREAD for a -single (arbitrary) thread synchronized at the barrier and zero for -each of the other threads. Otherwise, an error number shall be -returned to indicate the error. -

Errors

The pthread_barrier_wait function may fail if: -

EINVAL -: - The value specified by barrier does not refer to an - initialized barrier object. -

-This function shall not return an error code of [EINTR]. -

The following sections are informative. -

Examples

None. -

Application Usage

Applications using this function may be subject to priority -inversion, as discussed in the Base Definitions volume of -IEEE Std 1003.1-2001, Section 3.285, Priority Inversion. -

The pthread_barrier_wait function is part of the Barriers -option and need not be provided on all implementations. -

Pthreads-w32 defines _POSIX_BARRIERS to indicate -that this routine is implemented and may be used.

Rationale

None. -

Future Directions

None. -

Known Bugs

In - pthreads-win32, - pthread_barrier_wait may deadlock if the number of running - threads able to wait on the barrier object exceeds the value given - as the count parameter in - pthread_barrier_init(3). -

-See Also

pthread_barrier_destroy(3), -pthread_barrier_init(3), -the Base Definitions volume of IEEE Std 1003.1-2001, -<pthread.h> -

Copyright

Modified by Ross Johnson for use with Pthreads-w32.

Table of Contents

Name -
-
Synopsis -
-
Description -
-
Return - Value -
-
Errors -
-
Examples -
-
Application - Usage -
-
Rationale -
-
Future - Directions -
-
Known - Bugs -
-
See - Also -
-
Copyright -
-

- + + + + + "PTHREAD_BARRIER_WAIT"(P) manual page + + + + + + + + +

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_barrier_wait - synchronize at a barrier (ADVANCED +REALTIME THREADS) +

Synopsis

#include <pthread.h> +

int pthread_barrier_wait(pthread_barrier_t *barrier); + +

Description

The pthread_barrier_wait function shall synchronize +participating threads at the barrier referenced by barrier. +The calling thread shall block until the required number of threads +have called pthread_barrier_wait specifying the barrier. +

When the required number of threads have called +pthread_barrier_wait specifying the barrier, the constant +PTHREAD_BARRIER_SERIAL_THREAD shall be returned to one +unspecified thread and zero shall be returned to each of the +remaining threads. At this point, the barrier shall be reset to the +state it had as a result of the most recent pthread_barrier_init(3) +function that referenced it. +

The constant PTHREAD_BARRIER_SERIAL_THREAD is defined in +<pthread.h> and its value shall be distinct from any +other value returned by pthread_barrier_wait . +

The results are undefined if this function is called with an +uninitialized barrier. +

If a signal is delivered to a thread blocked on a barrier, upon +return from the signal handler the thread shall resume waiting at the +barrier if the barrier wait has not completed (that is, if the +required number of threads have not arrived at the barrier during the +execution of the signal handler); otherwise, the thread shall +continue as normal from the completed barrier wait. Until the thread +in the signal handler returns from it, it is unspecified whether +other threads may proceed past the barrier once they have all reached +it. +

A thread that has blocked on a barrier shall not prevent any +unblocked thread that is eligible to use the same processing +resources from eventually making forward progress in its execution. +Eligibility for processing resources shall be determined by the +scheduling policy. +

Return Value

Upon successful completion, the pthread_barrier_wait +function shall return PTHREAD_BARRIER_SERIAL_THREAD for a +single (arbitrary) thread synchronized at the barrier and zero for +each of the other threads. Otherwise, an error number shall be +returned to indicate the error. +

Errors

The pthread_barrier_wait function may fail if: +

EINVAL +: + The value specified by barrier does not refer to an + initialized barrier object. +

+This function shall not return an error code of [EINTR]. +

The following sections are informative. +

Examples

None. +

Application Usage

Applications using this function may be subject to priority +inversion, as discussed in the Base Definitions volume of +IEEE Std 1003.1-2001, Section 3.285, Priority Inversion. +

The pthread_barrier_wait function is part of the Barriers +option and need not be provided on all implementations. +

Pthreads-w32 defines _POSIX_BARRIERS to indicate +that this routine is implemented and may be used.

Rationale

None. +

Future Directions

None. +

Known Bugs

+ None. +

+See Also

pthread_barrier_destroy(3), +pthread_barrier_init(3), +the Base Definitions volume of IEEE Std 1003.1-2001, +<pthread.h> +

Copyright

Modified by Ross Johnson for use with Pthreads-w32.

Table of Contents

Name +
+
Synopsis +
+
Description +
+
Return + Value +
+
Errors +
+
Examples +
+
Application + Usage +
+
Rationale +
+
Future + Directions +
+
Known + Bugs +
+
See + Also +
+
Copyright +
+

+ \ No newline at end of file diff --git a/pthreads/manual/pthread_setschedparam.html b/pthreads/manual/pthread_setschedparam.html index 920c20bab..35fd7a268 100644 --- a/pthreads/manual/pthread_setschedparam.html +++ b/pthreads/manual/pthread_setschedparam.html @@ -1,113 +1,114 @@ - - - - - PTHREAD_SETSCHEDPARAM(3) manual page - - - - - - - -

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_setschedparam, pthread_getschedparam - control thread -scheduling -

parameters -

Synopsis

#include <pthread.h> -

int pthread_setschedparam(pthread_t target_thread, -int policy, const struct sched_param *param); -

int pthread_getschedparam(pthread_t target_thread, -int *policy, struct sched_param *param); -

Description

pthread_setschedparam sets the scheduling parameters for -the thread target_thread as indicated by policy and -param. policy can be either SCHED_OTHER -(regular, non-real-time scheduling), SCHED_RR (real-time, -round-robin) or SCHED_FIFO (real-time, first-in first-out). -param specifies the scheduling priority for the two real-time -policies.

Pthreads-w32 only supports SCHED_OTHER and does not support -the real-time scheduling policies SCHED_RR and SCHED_FIFO. -

pthread_getschedparam retrieves the scheduling policy and -scheduling parameters for the thread target_thread and stores -them in the locations pointed to by policy and param, -respectively. -

Return Value

pthread_setschedparam and pthread_getschedparam -return 0 on success and a non-zero error code on error. -

Errors

On error, pthread_setschedparam returns the following error -codes: -

ENOTSUP -: - policy is not SCHED_OTHER.
- EINVAL -: - One of the arguments is invalid, or the priority value specified by - param is not valid for the specified policy.
- ESRCH -: - The target_thread is invalid or has already terminated -

- -

-On error, pthread_getschedparam returns the following error -codes: -

ESRCH -: - the target_thread is invalid or has already terminated -

- -

-Author

Xavier Leroy <Xavier.Leroy@inria.fr> -

Modified by Ross Johnson for use with Pthreads-w32.

Name

pthread_setschedparam, pthread_getschedparam - control thread +scheduling +

parameters +

Synopsis

#include <pthread.h> +

int pthread_setschedparam(pthread_t target_thread, +int policy, const struct sched_param *param); +

int pthread_getschedparam(pthread_t target_thread, +int *policy, struct sched_param *param); +

Description

pthread_setschedparam sets the scheduling parameters for +the thread target_thread as indicated by policy and +param. policy can be either SCHED_OTHER +(regular, non-real-time scheduling), SCHED_RR (real-time, +round-robin) or SCHED_FIFO (real-time, first-in first-out). +param specifies the scheduling priority for the two real-time +policies.

Pthreads-w32 only supports SCHED_OTHER and does not support +the real-time scheduling policies SCHED_RR and SCHED_FIFO. +

pthread_getschedparam retrieves the scheduling policy and +scheduling parameters for the thread target_thread and stores +them in the locations pointed to by policy and param, +respectively. +

Return Value

pthread_setschedparam and pthread_getschedparam +return 0 on success and a non-zero error code on error. +

Errors

On error, pthread_setschedparam returns the following error +codes: +

ENOTSUP +: + policy is not SCHED_OTHER.
+ EINVAL +: + One of the arguments is invalid, or the priority value specified by + param is not valid for the specified policy.
+ ESRCH +: + The target_thread is invalid or has already terminated +

+ +

+On error, pthread_getschedparam returns the following error +codes: +

ESRCH +: + the target_thread is invalid or has already terminated +

+ +

+Author

Xavier Leroy <Xavier.Leroy@inria.fr> +

Modified by Ross Johnson for use with Pthreads-w32.

Name

pthread_win32_process_attach_np, -pthread_win32_process_detach_np, pthread_win32_thread_attach_np, -pthread_win32_thread_detach_np – exposed versions of the -pthreads-w32 DLL dllMain() switch functionality for use when -statically linking the library.

Synopsis

#include <pthread.h> -

BOOL pthread_win32_process_attach_np (void);

BOOL pthread_win32_process_detach_np (void);

BOOL pthread_win32_thread_attach_np (void);

BOOL pthread_win32_thread_detach_np (void);

Description

These functions contain the code normally run via dllMain -when the library is used as a dll but which need to be called -explicitly by an application when the library is statically linked.

You will need to call pthread_win32_process_attach_np -before you can call any pthread routines when statically linking. You -should call pthread_win32_process_detach_np before exiting -your application to clean up.

pthread_win32_thread_attach_np is currently a no-op, but -pthread_win32_thread_detach_np is needed to clean up the -implicit pthread handle that is allocated to a Win32 thread if it -calls certain pthreads routines. Call this routine when the Win32 -thread exits.

These functions invariably return TRUE except for -pthread_win32_process_attach_np which will return FALSE if -pthreads-w32 initialisation fails.

Cancellation

None.

Return Value

These routines return TRUE (non-zero) on success, or FALSE (0) if -they fail.

Errors

None.

Author

Ross Johnson for use with Pthreads-w32.

Table of Contents

Name -
-
Synopsis -
-
Description -
-
Cancellation -
-
Return - Value -
-
Errors -
-
Author -
-

- - + + + + + PTHREAD_WIN32_ATTACH_DETACH_NP manual page + + + + + + + +

POSIX Threads for Windows – REFERENCE - Pthreads-w32

Reference Index

Table of Contents

Name

pthread_win32_process_attach_np, +pthread_win32_process_detach_np, pthread_win32_thread_attach_np, +pthread_win32_thread_detach_np – exposed versions of the +pthreads-w32 DLL dllMain() switch functionality for use when +statically linking the library.

Synopsis

#include <pthread.h> +

BOOL pthread_win32_process_attach_np (void);

BOOL pthread_win32_process_detach_np (void);

BOOL pthread_win32_thread_attach_np (void);

BOOL pthread_win32_thread_detach_np (void);

Description

These functions contain the code normally run via dllMain +when the library is used as a dll but which need to be called +explicitly by an application when the library is statically linked. As of version 2.9.0, the static library built using either MSC or GCC includes RT hooks which will call the pthread_win32_process_*_np routines automatically on start/exit of the application.

You will need to call pthread_win32_process_attach_np +before you can call any pthread routines when statically linking. You +should call pthread_win32_process_detach_np before exiting +your application to clean up.

pthread_win32_thread_attach_np is currently a no-op, but +pthread_win32_thread_detach_np is needed to clean up the +implicit pthread handle that is allocated to a Win32 thread if it +calls certain pthreads routines. Call this routine when the Win32 +thread exits.

These functions invariably return TRUE except for +pthread_win32_process_attach_np which will return FALSE if +pthreads-w32 initialisation fails.

Name +
+
Synopsis +
+
Description +
+
Cancellation +
+
Return + Value +
+
Errors +
+
Author +
+

+ + -- cgit v1.2.3