Message-ID:	<3E494CCA.12E70A43@yahoo.com>
From:	CBFalconer <cbfalconer AT yahoo DOT com>
Organization:	Ched Research
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: how to make a Timer
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1030210075002 DOT 7932C AT is> <b29tp3$1agvkq$1 AT ID-79865 DOT news DOT dfncis DOT de> <3e489301 DOT sandmann AT clio DOT rice DOT edu> <%v22a.45175$jM5 DOT 113869 AT newsfeeds DOT bigpond DOT com> <3E48F219 DOT 8FB9B40B AT yahoo DOT com> <dP72a.45469$jM5 DOT 114036 AT newsfeeds DOT bigpond DOT com>
Lines:	19
Date:	Tue, 11 Feb 2003 19:44:49 GMT
NNTP-Posting-Host:	12.90.177.83
X-Complaints-To:	abuse AT worldnet DOT att DOT net
X-Trace:	bgtnsc04-news.ops.worldnet.att.net 1044992689 12.90.177.83 (Tue, 11 Feb 2003 19:44:49 GMT)
NNTP-Posting-Date:	Tue, 11 Feb 2003 19:44:49 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Ben Peddell wrote:
> 
> > Please do not toppost.  RDTSC will cause a bad opcode trap on a
> > 486, or a 386, both of which are suitable processors for the DJGPP
> > system.  Bad idea.
> 
> My idea is that the uclock() checks whether rdtsc is available when it is
> first called. And, if it's available the use it. If it's not, don't.

If suitably guarded my objections go away.  There are ways of
checking CPU type that do not provoke crashes, but I don't have my
finger on them.

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!

- Raw text -