search for: clock_process_cputime_id

On 01/24/16 12:29 PM, Erik de Castro Lopo wrote:> Dave Yeo wrote: > >> After this the build dies with, >> util.c: In function 'benchmark_function': >> util.c:124:17: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first use >> in this function) >> clock_gettime (CLOCK_PROCESS_CPUTIME_ID, &start) ; >> >> Would using gettimeofday() be accurate enough? > > AS a fall back yes, but not as replacement on platforms with clock_gettime(). > >> Perhaps...

I''m continuing to investigate the usage of rdtsc in userspace and whether there are programs "out there" that use it "unsafely" that might randomly break under Xen if rdtsc is not emulated, e.g. across a migration. Some have argued that nobody should use rdtsc and any programs that use rdtsc directly are "fundamentally broken" so the default for rdtsc

HI all, I think its time for a new release. The current code base is stable and I've been building it for x86_64/linux, powerpc/linux, armhf/linux, x86_64/darwin in a Jenkins build bot. I'm pretty sure others have been building regularly on their platforms of interest. I made a first pass on an update to the changelog.html. I' also putting toether a release checklist that I will add

...ached patch works around this. Not the best solution as best would be configure tests, but simple. I'll file a bug about this but it'll be a while before anything is done about it. After this the build dies with, util.c: In function 'benchmark_function': util.c:124:17: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first use in this function) clock_gettime (CLOCK_PROCESS_CPUTIME_ID, &start) ; Would using gettimeofday() be accurate enough? Perhaps simpler just to disable the microbench test on OS/2 as gettimeofday() would require a configure test and OS/2 is a minor platform? Dave -...

Dave Yeo wrote: > On 01/24/16 12:29 PM, Erik de Castro Lopo wrote:> Dave Yeo wrote: > > > >> After this the build dies with, > >> util.c: In function 'benchmark_function': > >> util.c:124:17: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first use > >> in this function) > >> clock_gettime (CLOCK_PROCESS_CPUTIME_ID, &start) ; > >> > >> Would using gettimeofday() be accurate enough? > > > > AS a fall back yes, but not as replacement on platforms with clock_gett...

...+ +struct itimerval { + struct timeval_old it_interval; + struct timeval_old it_value; +}; + +struct timezone { + int tz_minuteswest; + int tz_dsttime; +}; + +#define ITIMER_REAL 0 +#define ITIMER_VIRTUAL 1 +#define TIMER_PROF 2 + +#define CLOCK_REALTIME 0 +#define CLOCK_MONOTONIC 1 +#define CLOCK_PROCESS_CPUTIME_ID 2 +#define CLOCK_THREAD_CPUTIME_ID 3 +#define CLOCK_MONOTONIC_RAW 4 +#define CLOCK_REALTIME_COARSE 5 +#define CLOCK_MONOTONIC_COARSE 6 +#define CLOCK_BOOTTIME 7 +#define CLOCK_REALTIME_ALARM 8 +#define CLOCK_BOOTTIME_ALARM 9 +#define CLOCK_TAI 11 + +#define TIMER_ABSTIME 0x01 /* The...

...: not found Checking for library rt : yes Checking for clock_gettime : ok Checking whether the clock_gettime clock ID CLOCK_MONOTONIC is available : ok Checking whether the clock_gettime clock ID CLOCK_PROCESS_CPUTIME_ID is available : ok Checking whether the clock_gettime clock ID CLOCK_REALTIME is available : ok Checking for struct timespec : ok Checking for header arpa/nameser.h : yes Checking for header...

...r... no checking for dirfd... yes checking for dirfd declaration... yes checking a usable readdir()... yes checking crypt.h usability... yes checking crypt.h presence... yes checking for crypt.h... yes checking for library containing crypt... -lcrypt checking for CLOCK_MONOTONIC... yes checking for CLOCK_PROCESS_CPUTIME_ID... yes checking for CLOCK_REALTIME... yes checking for struct timespec type... yes checking for printf... yes checking for memset... yes checking for memcpy... yes LIBREPLACE_BROKEN_CHECKS: END checking for syslog... yes LIBREPLACE_NETWORK_CHECKS: START checking sys/socket.h usability... yes checki...