Yes, that sounds like a better solution.
I will table this issue for now, since there are probably other problems
with those two examples as well.
It might not be a bad idea to put some
sort of warning in the code so that people are not surprised if the program
doesn't work. Something like:
"T
Corey,
On Fri, Jan 9, 2009 at 1:29 AM, Corey Ashford
wrote:
> Hi Stephan,
>
> As you might have guessed, one of our goals has been to be able to run the
> libpfm examples cleanly on Power.
>
> multiplex.c gives odd error messages about calls to pfm_write_pmds and
> pfm_write_pmcs depending on the
Hi Stephan,
As you might have guessed, one of our goals has been to be able to run
the libpfm examples cleanly on Power.
multiplex.c gives odd error messages about calls to pfm_write_pmds and
pfm_write_pmcs depending on the options given. I tracked this down to
the allocation of the all_pmcs
