Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
From:	N8TM AT aol DOT com
Message-ID:	<0.bfd56fee.252fecbb@aol.com>
Date:	Fri, 8 Oct 1999 20:56:27 EDT
Subject:	clock() resolution problem on an HP NT box
To:	cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0
X-Mailer:	Windows AOL sub 26

The clock() function on my HP X550, both in NT4SP5 and linux, has 1 second 
resolution, like DOS.  I've been forced to hack the timer calls to use 
QueryPerformance...() calls as if I were running W95, and shut down to a 
single thread job to do performance timing.  However, -pg appears to get 
useful results.  Is there a way to make clock() work on such a box?

Tim
tprince AT computer DOT org

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -