X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F6AF34A.4040301@lysator.liu.se> Date: Thu, 22 Mar 2012 10:39:22 +0100 From: Peter Rosin User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: clock_getres(CLOCK_REALTIME, .) may return an outdated and too high resolution References: <4F6A5D42 DOT 3030108 AT t-online DOT de> <20120322093340 DOT GW18032 AT calimero DOT vinschen DOT de> In-Reply-To: <20120322093340.GW18032@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen skrev 2012-03-22 10:33: > On Mar 21 23:59, Christian Franke wrote: >> BTW: GetSystemTimeAsFileTime() apparently provides the same >> resolution (at least on Win7 x64). So the more complex use of >> SharedUserData.InterruptTime may have less benefit than expected. > > On pre-Vista, the accuracy of GetSystemTimeAsFileTime is 15.625 ms, > fixed. On Vista and later it seems to be 15ms or better, but its > resultion is not constant anymore. I have definite memories of an (albeit odd) XP laptop with 10 ms accuracy. But that was years ago. Hmmm? Cheers, Peter -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple