Blame man/man3/PAPI_register_thread.3
Branch: 57771707c5d17696fd3660ed6f10428b3c234e9a
Packit
577717
.TH "PAPI_register_thread" 3 "Mon Dec 18 2017" "Version 5.6.0.0" "PAPI" \" -*- nroff -*-
Packit
577717
.ad l
Packit
577717
.nh
Packit
577717
.SH NAME
Packit
577717
PAPI_register_thread \-
Packit
577717
.PP
Packit
577717
Notify PAPI that a thread has 'appeared'\&.
Packit
577717
Packit
577717
.SH SYNOPSIS
Packit
577717
.br
Packit
577717
.PP
Packit
577717
.SH "Detailed Description"
Packit
577717
.PP
Packit
577717
Packit
577717
.PP
Packit
577717
\fBC Interface:\fP
Packit
577717
.RS 4
Packit
577717
#include <\fBpapi\&.h\fP>
Packit
577717
.br
Packit
577717
int \fBPAPI_register_thread\fP (void);
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
\fBPAPI_register_thread()\fP should be called when the user wants to force PAPI to initialize a thread that PAPI has not seen before\&.
Packit
577717
.PP
Packit
577717
Usually this is not necessary as PAPI implicitly detects the thread when an eventset is created or other thread local PAPI functions are called\&. However, it can be useful for debugging and performance enhancements in the run-time systems of performance tools\&.
Packit
577717
.PP
Packit
577717
\fBReturn values:\fP
Packit
577717
.RS 4
Packit
577717
\fIPAPI_ENOMEM\fP Space could not be allocated to store the new thread information\&.
Packit
577717
.br
Packit
577717
\fIPAPI_ESYS\fP A system or C library call failed inside PAPI, see the errno variable\&.
Packit
577717
.br
Packit
577717
\fIPAPI_ECMP\fP Hardware counters for this thread could not be initialized\&.
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
\fBSee Also:\fP
Packit
577717
.RS 4
Packit
577717
\fBPAPI_unregister_thread\fP
Packit
577717
.PP
Packit
577717
\fBPAPI_thread_id\fP
Packit
577717
.PP
Packit
577717
\fBPAPI_thread_init\fP
Packit
577717
.RE
Packit
577717
.PP
Packit
577717
Packit
577717
Packit
577717
.SH "Author"
Packit
577717
.PP
Packit
577717
Generated automatically by Doxygen for PAPI from the source code\&.