PAPI_thread_init(3)

📦
version 7.2.0 · 8 versions
, in nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu resolute, ubuntu stonking

💖 PAPI_thread_init(3) — the PAPI manual page, bestie 💖

✨ NAME ✨

PAPI_thread_init — initialize thread support in the PAPI library.

🌸 SYNOPSIS 🌸

The real synopsis tea is all in the Detailed Description below, bestie. Keep scrolling. 💅

🌈 Detailed Description 🌈

🎀 Parameters 🎀

  • *id_fn — pointer to a function that returns current thread ID.

PAPI_thread_init initializes thread support in the PAPI library. Applications that make no use of threads do not need to call this routine. 🫶

This function MUST return a UNIQUE thread ID for every new thread/LWP created. No cap. 🚨

The OpenMP call omp_get_thread_num() violates this rule, because the underlying LWPs may have been killed off by the run-time system or by a call to omp_set_num_threads(). 😭 In that case, it may still be possible to use omp_get_thread_num() in conjunction with PAPI_unregister_thread() when the OpenMP thread has finished. But honestly? It is much better to use the underlying thread subsystem’s call, which is pthread_self() on Linux platforms. Slay. 🐧✨

       if ( PAPI_thread_init(pthread_self) != PAPI_OK )
           exit(1);

That’s the whole vibe check: if it’s not PAPI_OK, you bail. 💀

🔗 See also 🔗

  • PAPI_register_thread
  • PAPI_unregister_thread
  • PAPI_get_thr_specific
  • PAPI_set_thr_specific
  • PAPI_thread_id
  • PAPI_list_threads

👑 Author 👑

Generated automatically by Doxygen for PAPI from the source code.

This page came from the PAPI source, version 7.2.0.0, dated Wed Jun 25 2025 19:30:49. PAPI_thread_init(3) signing off — mwah 💋🎀

📦 where this page comes from