GitLab

Now, one can select which kind of measurements are taken by calling the
member functions %measure_flops, and %measure_memory of a timer_t
object. For example

  type(timer_t) :: timer

  call timer%measure_flops(.true.)
  call timer%measure_memory(.true.)

  call timer%enable()

An explicit ftimings_init() call is now no longer necessary, PAPI will
be initialized on the first %measure_flops(.true.) call.

Otherwise, very fast routines are simply not printed

If the argument 'name' is not given to timer_stop, close the currently
active region without further sanity checking.

Next so some refactoring into four separate source files, support for
also recording values of perfomance counters via the PAPI library was
added, at the moment a FLOP count is measured and results are presented
in timer_print as MFlop/s.

Make only timer_t visible via the module, some cleanup

The resulting package is called ftimings-$(FTIMINGS_API_VERSION)-$(FC)