PAPIF_unregister_thread(3)
β¨ NAME β¨
PAPIF_unregister_thread β bestie, this is your little heads-up to PAPI that a thread has 'disappeared'. Like, it's gone gone. Notify the library so it can keep its vibes accurate. π«
π SYNOPSIS π
Okay so here's the whole breakdown, no gatekeeping:
π Detailed Description
Fortran Interface:
#include 'fpapi.h'
PAPIF_unregister_thread( C_INT check )
That's it, that's the whole call. You pass in check, it's a C_INT, and honestly? Iconic of it. π
π See also
PAPI_unregister_threadβ the C-side sibling, go look at it too fr fr π«Ά
π¦ Author π¦
Generated automatically by Doxygen for PAPI from the source code. Not a human author, just the Doxygen girlies doing their thing on autopilot, and we respect the grind. π€β¨
lowkey important: this page is from the PAPI manual, section 3, so you know exactly where you are. Don't lose the plot.
And that's the page, bestie! Version 7.2.0.0, dated Wed Jun 25 2025 19:30:49 β go forth and unregister those threads responsibly, mwah π
ππΈ
π¦ where this page comes from
- nixos 26.05: papi 7.2.0
- nixpkgs unstable: papi 7.2.0
- opensuse-leap 16.0: papi-devel 7.2.0-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: papi-devel 7.2.0-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: papi-devel 7.2.0-160000.2.2 Β· BSD-3-Clause
- ubuntu resolute: libpapi-dev 7.2.0-2 Β· BSD-3-Clause
- ubuntu stonking: libpapi-dev 7.2.0-2 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms