Class PAPI_add_event: The vector function should take a pointer to a length argument so a proper return value can be set upon partial success.
Class PAPI_add_events: The vector function should take a pointer to a length argument so a proper return value can be set upon partial success.
Class PAPI_add_named_event: The vector function should take a pointer to a length argument so a proper return value can be set upon partial success.
Class PAPI_cleanup_eventset: If the user has set profile on an event with the call, then when destroying the EventSet the memory allocated by will not be freed. The user should turn off profiling on the Events before destroying the EventSet to prevent this behavior.
Class PAPI_destroy_eventset: If the user has set profile on an event with the call, then when destroying the EventSet the memory allocated by will not be freed. The user should turn off profiling on the Events before destroying the EventSet to prevent this behavior.
Class PAPI_disable_component_by_name: none known
Class PAPI_enum_dev_type: none known
Class PAPI_get_component_index: Doesn't work for preset events
Class PAPI_get_dev_attr: none known
Class PAPI_get_dev_type_attr: none known
Class PAPI_get_event_component: Doesn't work for preset events
Class PAPI_get_hardware_info: If called before initialization the behavior of the routine is undefined.
Class PAPI_get_overflow_event_index: This function may not return all overflowing events if used with software-driven overflow of multiple derived events. PAPI_get_overflow_event_index decomposes an overflow_vector into an event index array in which the first element corresponds to the least significant set bit in overflow_vector and so on. Based on overflow_vector, the user can only tell which physical counters overflowed. Using this function, the user can map overflowing counters to specific events in the event set. An array is used in this function to support the possibility of multiple simultaneous overflow events.
Class PAPI_get_shared_lib_info: If called before initialization the behavior of the routine is undefined.
Class PAPI_is_initialized: If you don't call this before using any of the low level PAPI calls, your application could core dump.
Class PAPI_library_init: If you don't call this before using any of the low level PAPI calls, your application could core dump.
Class PAPI_num_cmp_hwctrs: This count may include fixed-use counters in addition to the general purpose counters.
Class PAPI_profil: If you call PAPI_profil, PAPI allocates buffer space that will not be freed if you call PAPI_shutdown or PAPI_cleanup_eventset. To clean all memory, you must call PAPI_profil on the Events with a 0 threshold.
Class PAPI_remove_events: The last argument should be a pointer so the count can be returned on partial success in addition to a real error code.