Date: Fri, 08 Jun 2001 09:56:04 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: tlambert2@mindspring.com Cc: Erik Trulsson <ertr1013@student.uu.se>, arch@FreeBSD.ORG Subject: Re: time_t definition is worng Message-ID: <4346.991986964@critter> In-Reply-To: Your message of "Fri, 08 Jun 2001 00:12:11 PDT." <3B207ACB.70A84C54@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3B207ACB.70A84C54@mindspring.com>, Terry Lambert writes: >Poul-Henning Kamp wrote: >> Instead lets set a deadline: The longest commonly used time interval >> is 30 years for mortgages, so lets be safe and say that on january >> 1st 2005 00:00 UTC we will transition time_t to be at least 33 >> bits. Until then it is 32 bits. >> >> In practice this will probably be 64 bits on most arch's but let >> us use the 33 bit goal rather than mandate 64bits which might be >> prohibitively expensive on some architecturs. >> >> Any objections ? > >Yeah; > >Are you going to write the FS conversion tool? > >Ask Kirk why there were 32 bit reserved fields immediately >adjacent to the existing 32 bit time fields, before someone >decided that all times (and not just the modification time, >used by "make") needed to have nanoseconds, and that was >more important than having the transition in 2038 go without >a hitch. Actually a 64 bit timeformat could be constructed like this: 1 bit sign 33 bit seconds 30 bits fraction of seconds This would give us a range of +/- 272 years and a resolution of .93 nanoseconds. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4346.991986964>