PAPIf_hl_region_end(3)

💅 PAPIf_hl_region_end(3) — the PAPI manual, but make it bestie-coded 🎀

✨ NAME ✨

PAPIf_hl_region_end — reads and stores hardware events at the end of an instrumented code region. It's literally the closing-bracket era for your PAPI high-level region, bestie 💖

💫 SYNOPSIS 💫

Detailed Description

Fortran Prototype:

#include 'fpapi.h'
PAPIf_hl_region_end( C_STRING region, C_INT check )

Parameters

• region — a unique region name corresponding to PAPIf_hl_region_begin 🎀

Return values

• PAPI_OK — that's the whole entry in the original list, bestie 💅
• 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 💀
• PAPI_ENOMEM — Insufficient memory 🌸

So here's the tea: PAPIf_hl_region_end reads hardware events and stores the difference to the values from PAPIf_hl_region_begin at the end of an instrumented code region. It assumes that PAPIf_hl_region_begin was called before — like, it's counting on you to have started the region first 🫶. Also note: an output is automatically generated when your application terminates. Yes, it handles the final paperwork for you ✨.

🍓 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_region_end("computation", retval)
if ( retval .NE. PAPI_OK ) then
    write (*,*) "PAPIf_hl_region_end failed!"
end if

🔎 See also 🔎

• PAPI_hl_region_end

✍️ Author ✍️

Generated automatically by Doxygen for PAPI from the source code. No cap, that's literally the author line 💅

---

Sign-off: Version 7.2.0.0 • Wed Jun 25 2025 19:30:49 — generated automatically by Doxygen for PAPI from the source code. Bye bestie, go instrument those regions 💖🦋✨