Differences

This shows you the differences between two versions of the page.

--- doku:papi_ir [2016/07/06 12:10] – [Practical tips:] ir
+++ doku:papi_ir [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 27: / Line 27: @@
 ==== Interfacing with PAPI : Low level interface ====
-In general, some code section to be analyzed with PAPI needs to be wrapped into a sequence of standard PAPI calls, e.g., like in the following examples for
+In general, some code section to be analyzed with PAPI needs to be wrapped into a sequence of standard PAPI calls.
-  * [[doku:papi_ll_c|C]] or
+Here, code examples for
-  * [[doku:papi_ll_Fortran|Fortran]].
+  * [[doku:papi_ll_c|C users]] and
+  * [[doku:papi_ll_Fortran|Fortran users]] can be found.
 As stated in the comment of the C code above, it is best to analyze one particular event at a time. This advice is given because the CPU has limitations in combining arbitrary counters at a time.
 ==== Interfacing with PAPI : High level interface ====
-The high level API combines the counters for a specified list of PAPI preset events, only. The set of implemented high level functions is quite limited and can be found in the section ''The High Level API'' next to the last paragraph of ''papi.h''.
+The high-level API combines the counters for a specified list of PAPI preset events, only. The set of implemented high level functions is quite limited and can be found in the section ''The High Level API'' next to the last paragraph of ''papi.h''. It can also be used in conjunction with the low-level API. An example of the usage of the high level API can be found here [[doku:papi_hl_c|for C users]].
-The high level API can also be used in conjunction with the low level API.
-Example code:
-  * [[doku:papi_hl_c|C]]
-  * [[doku:papi_hl_fortran|Fortran]]
 ==== Practical tips: ====
   * A quick overview of supported events and corresponding PAPI variables for a particular type of CPU is obtained from executing command ''papi_avail''.