This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12515] clock() does not provide the advertised precision
- From: "stephane at magnenat dot net" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 24 Feb 2011 12:52:15 +0000
- Subject: [Bug libc/12515] clock() does not provide the advertised precision
- Auto-submitted: auto-generated
- References: <bug-12515-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12515
StÃphane Magnenat <stephane at magnenat dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
Ever Confirmed|1 |0
--- Comment #2 from StÃphane Magnenat <stephane at magnenat dot net> 2011-02-24 12:52:10 UTC ---
Thank you for your quick answer!
I see the difference. Could it still be possible to make the "legacy"
interface, clock(), to provide a higher precision than what it does now? Maybe
by building it on top of clock_gettime(CLOCK_PROCESS_CPUTIME_ID, ...)? For
normal people, it is very inconvenient that "simple" calls do not provide high
resolution. As I said, it is a bit sad to have to re-implement boost::timer().
Of course, one could say that it is boost's problem, but as clock() is the
simple C interface, it would be nice for it to provide the maximum available
precision, that would make normal users happy :-)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.