From: Nathan Sidwell <nathan@codesourcery.com>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: gcc <gcc-help@gcc.gnu.org>, gcc@gcc.gnu.org
Subject: Re: Accuracy of clock
Date: Wed, 24 Nov 2004 15:35:00 -0000 [thread overview]
Message-ID: <41A4990D.30506@codesourcery.com> (raw)
In-Reply-To: <20041124070826.62054.qmail@web52904.mail.yahoo.com>
Ankit Jain wrote:
> I want to confirm if the clock like gettimeofday or
> clock_gettime has any bugs and if then how much
> inaccurate are these clock. i want to know the time
> taken by my program in microseconds
there is at least one bug in the set of all 'gettimeofday' functions that
have ever existed :)
* you are in the wrong place, ask somewhere relevent to your system
* you do not specify your system, so you'll need to determine that
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2004-11-24 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 7:59 Ankit Jain
2004-11-24 15:35 ` Nathan Sidwell [this message]
2004-11-25 7:15 ` Ankit Jain
2004-11-25 8:42 ` Andrew Pinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A4990D.30506@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=ankitjain1580@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).