Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-WM-Posted-At: avacado.atomice.net; Thu, 9 May 02 00:23:50 +0100 Message-ID: <018001c1f6e7$6924c420$0100a8c0@advent02> From: "Chris January" To: References: <15547 DOT 16136 DOT 163472 DOT 840007 AT bea DOT com><20020415214133 DOT GA19612 AT redhat DOT com> <15577 DOT 12319 DOT 622365 DOT 566799 AT bea DOT com> Subject: Re: [PATCH] gettimeofday time travels Date: Thu, 9 May 2002 00:23:50 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > > >How about the attached quick and dirty fix? > > > > I'm sorry but I don't think a quick and dirty fix is justified if > > there are other alternatives. I haven't seen any other alternatives > > discussed yet. > > No other alternatives have been proposed. I'm aware of a couple of > other XEmacs'ers who are plagued by this (we love our uptime). > > I don't believe my patch to be dirtier than the implementation (no > offence intended!). Please reconsider it. On Windows NT, you can use the ZwQuerySystemInformation internal call with the SystemTimeOfDayInformation structure to get the current time of day at a greater resolution than you can with the Performance counters. I'm not sure about the granularity though - that's something that would have to be tested. However the value doesn't suffer from time-travelling problems. If indeed the granularity is too coarse, you could still use the value to check that the QueryPerformanceCounters value is sane (which is what I believe this discussion was originally about). Regards Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/