PAPIf_hl_read(3)

PAPIf_hl_read(3) — PAPI manual, bestie 💅

NAME

PAPIf_hl_read — reads and stores hardware events inside of an instrumented code region. That’s the vibe: hardware events go in, storage happens internally, and the region is instrumented. 💖

SYNOPSIS

Detailed Description

Fortran Prototype:

#include <fpapi.h>
int PAPIf_hl_read( C_STRING region, C_INT check )

Parameters

• region — a unique region name corresponding to PAPIf_hl_region_begin. That’s the parameter listed here, bestie. 🎀

Return values

• PAPI_OK
• PAPI_ENOTRUN — EventSet is currently not running or could not determined.
• PAPI_ESYS — A system or C library call failed inside PAPI, see the errno variable.
• PAPI_EMISC — PAPI has been deactivated due to previous erros. (Yes, erros is exactly what the page says. 🫶)
• PAPI_ENOMEM — Insufficient memory.

So like, PAPIf_hl_read reads hardware events and stores them internally inside of an instrumented code region. It assumes that PAPIf_hl_region_begin was called before. That’s the assumption, bestie — no cap. 🔥

Example

Example:

integer retval

call PAPIf_hl_region_begin("computation", retval)
if ( retval .NE. PAPI_OK ) then
    write (*,*) "PAPIf_hl_region_begin failed!"
end if

!do some computation here

call PAPIf_hl_read("computation", retval)
if ( retval .NE. PAPI_OK ) then
    write (*,*) "PAPIf_hl_read failed!"
end if

!do some computation here

call PAPIf_hl_region_end("computation", retval)
if ( retval .NE. PAPI_OK ) then
    write (*,*) "PAPIf_hl_region_end failed!"
end if

See also

• PAPI_hl_read

Author

Generated automatically by Doxygen for PAPI from the source code. (automation ate, honestly. 🤖✨)

---

Sign-off: this page is from PAPI version 7.2.0.0, dated Wed Jun 25 2025 19:30:49, and it’s the PAPIf_hl_read(3) page saying bye bestie 💜🦋