Date:	Thu, 6 Feb 1997 19:05:56 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Till Harbaum <harbaum AT ra DOT ibr DOT cs DOT tu-bs DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: Strange Timer with DJGPP
In-Reply-To:	<yksohdyfc2i.fsf@ra.ibr.cs.tu-bs.de>
Message-ID:	<Pine.SUN.3.91.970206185859.6081B-100000@is>
MIME-Version:	1.0

On 6 Feb 1997, Till Harbaum wrote:

> While running any DJGPP compiled program (own tools, gnu tools
> or gcc itself) my system timer speeds up a little.

Even if that program doesn't call any of the time-related functions? 
let's say you write a trivial hello world program with a quirk: after
printing the message it doesn't exit, but waits for a key to be
pressed--is your timer sped up by such a program too?  If so, I'd say it's
impossible that the DJGPP programs are the cause.  I don't think the
functions linked into the minimal program do anything with the system
timer.  If you want to be sure, run `nm' on your executable (output of the
linker) and check the sources of every function linked in.

> It is the timer handlers job to clear its counter at midnight and 
> to increase the date. Is this missing in djgpp?

AFAIK, DJGPP doesn't install a handler for the timer tick interrupt unless 
you compile with -pg.  If this weirdness happens for programs compiled 
without -pg, I'd say the most probable cause is the DPMI host (which one 
do you use, btw?).

> Another explanation would be: My pc got caught in a time trap!

It happens...

- Raw text -