 |
 |
Hi Van, Hi Aleks, Again, just to point out that one of the best options for doing serious timing (and also accessing hardware counters to get the FLIPs/sec. cache misses and all that sorts of other stuff) is to use PAPI (which has Fortran and C support) and that with very simple calls can profile specific function(s) performance. Here is the man page for what Aleks Donev wants (Wall clock): http://icl.cs.utk.edu/projects/papi/files/html_man/papi_get_real_cyc.html And here is the PAPI documentation: http://icl.cs.utk.edu/projects/papi/ Answering Van Snyder's question about Glib: No, they use gettimeofday(): http://cvs.gnome.org/lxr/source/glib/gtimer.c Cheers, Alan On Tue, 23 Jul 2002, Van Snyder wrote: > Alan Aspuru-Guzik <[log in to unmask]> wrote: > > > Dear Alex (Pafu!), > > > > A *very* portable alternative is GLIB. > > http://developer.gnome.org/doc/API/glib/ > > Many years ago, for DOS on x86, I wrote a timer routine that used the BIOS > clock + all of the bits of the timer that ticked at 1193182/sec, to get > high-resolution timing. The timer routine didn't subtract its own cost, > but it sure was better than the .01 second resolution most timers offer > now. I'm happy to send it to anybody who wants it. > > Does g_timer do this well? > > -- Alan Aspuru-Guzik Dios mueve al jugador, y éste, la pieza. (510)642-5911 UC Berkeley ¿Qué Dios detrás de Dios la trama empieza (925)422-8739 LLNL de polvo y tiempo y sueño y agonías? -Borges