On Tue, 30 May 2017, William Cohen wrote: > As a workaround I have been developing a patch that avoids using the > PFM_PMU_MAX and examines the pfm_pmu_get_info return code to determine > if there are might be additional pmu descriptions to scan. Attached is > the patch. I have tried it out. It compiles and appears to allow papi > to not care so much about which particular libpfm was used to build > papi.
The patch is a little more intrusive than I was hoping for, but I'll see that it (or something like it) gets applied. Is there a quick way of testing it? Were you using papi_component_avail or something else? Mostly your use of forever-looping for loops throws me, I'm more used to a while(1) type idiom. Vince ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
