> Le 12 oct. 2018 à 17:27, Bruno Haible <br...@clisp.org> a écrit : > > Hi Akim, > > This patch looks good, except for two things: > - The module description still references m4/timevar.m4, which no longer > exists. Fixed, thanks! > - The code prints the '.wall' values, which are not initialized. But this > is fixed in part 3/3. They are initialized static void set_to_current_time (struct timevar_time_def *now) { now->user = 0; now->sys = 0; now->wall = 0; but yes, they are no yet filled with actual values. Is this really a problem?
- Re: timevar: further work Bruno Haible
- Re: timevar: further work Bruno Haible
- Re: timevar: further work Akim Demaille
- Re: timevar: further work Bruno Haible
- Re: timevar: further work Akim Demaille
- Re: timevar: further work Bruno Haible
- Re: timevar: further work Akim Demaille
- Re: timevar: further work Akim Demaille
- Re: timevar: 1/3: expect that getrusage is avai... Akim Demaille
- Re: timevar: 1/3: expect that getrusage is avai... Bruno Haible
- Re: timevar: 1/3: expect that getrusage is avai... Akim Demaille
- Re: timevar: 1/3: expect that getrusage is avai... Bruno Haible
- Re: timevar: 2/3: improve the output format Akim Demaille
- Re: timevar: 2/3: improve the output format Bruno Haible
- Re: timevar: 3/3: use clock_gettime to get wall... Akim Demaille
- Re: timevar: 3/3: use clock_gettime to get wall... Bruno Haible
- Re: timevar: 3/3: use clock_gettime to get wall... Akim Demaille
- Re: timevar: 3/3: use clock_gettime to get wall... Bruno Haible
- Re: timevar: 3/3: use clock_gettime to get wall... Akim Demaille
- Re: timevar: 3/3: use clock_gettime to get wall... Bruno Haible
- Re: timevar: 3/3: use clock_gettime to get wall... Akim Demaille