On 09/09/14 10:01, Rémi Denis-Courmont wrote: > Why would it be more robust? Unless the libc is utterly broken, the > result will be the same. Indeed I believe glibc's sysconf() calls > clock_getres() internally.
Why would be unavailable? Is it possible to disable it at runtime? > pthread_once() and a clockid_t static variable are perfectly suited here. Willing to bake a patch? lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
