Lines Matching refs:specific

468 The @code{tss_t} data type identifies a thread-specific storage
476 (void *)}, to be used as a thread-specific storage destructor.  The
505 @code{tss_create} creates a new thread-specific storage key and stores
524 @code{tss_set} sets the value of the thread-specific storage
535 thread-specific storage for the current thread.  Different threads may
543 @code{tss_delete} destroys the thread-specific storage identified by
555 * Thread-specific Data::          Support for creating and
556 				  managing thread-specific data
561 @node Thread-specific Data
562 @subsection Thread-specific Data
565 data specific to a thread.  Such data may be destroyed at thread exit,
574 Create a thread-specific data key for the calling thread, referenced by
578 before thread-specific data, so they should not be used in thread-specific
579 data destructors or even as members of the thread-specific data, since the
590 Destroy the thread-specific data @var{key} in the calling thread.  The
591 destructor for the thread-specific data is not called during destruction, nor
599 Return the thread-specific data associated with @var{key} in the calling
614 Associate the thread-specific @var{value} with @var{key} in the calling thread.
632 * Restartable Sequences::                 Linux-specific restartable sequences
720 It is possible to create a new thread with a specific signal mask