From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP and Y2K (was: RHIDE compiles all files)
Date:	Mon, 18 Oct 1999 18:56:20 +0200
Organization:	NetVision Israel
Lines:	15
Message-ID:	<Pine.SUN.3.91.991018185252.6354A-100000@is>
References:	<7ua0d4$b38$1 AT nnrp1 DOT deja DOT com> <7ue8u7$igh$1 AT solomon DOT cs DOT rose-hulman DOT edu> <Pine DOT SUN DOT 3 DOT 91 DOT 991018104606 DOT 3777V-100000 AT is> <7ufao3$lv0$1 AT solomon DOT cs DOT rose-hulman DOT edu>
NNTP-Posting-Host:	is.elta.co.il
Mime-Version:	1.0
X-Trace:	news.netvision.net.il 940265705 9807 199.203.121.2 (18 Oct 1999 16:55:05 GMT)
X-Complaints-To:	abuse AT netvision DOT net DOT il
NNTP-Posting-Date:	18 Oct 1999 16:55:05 GMT
X-Sender:	eliz AT is
In-Reply-To:	<7ufao3$lv0$1@solomon.cs.rose-hulman.edu>
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 18 Oct 1999, Damian Yerrick wrote:

> Does DJGPP include some special workarounds to
> circumvent BIOS bugs? Or do its GCC roots give it
> a Y2038 bug?

Neither.

DJGPP's time_t variable wraps around only in 21xx year (I think xx=26, 
but I forget the details; you can easily test this yourself, though).

As for the BIOS, if you really mean one of those BIOSes that jump 
back at 31-12-1999, then this might indeed be a problem, but it is
easily corrected.  And I have yet to see a 486 that has this problem.

- Raw text -