[y2038] r183 committed - Mention 10.6's gmtime(-2**52) bug

0 views

Skip to first unread message

codesite...@google.com

unread,

Feb 5, 2010, 3:50:24 AM2/5/10

to y2038-...@googlegroups.com

Revision: 183
Author: schwern
Date: Fri Feb 5 00:49:24 2010
Log: Mention 10.6's gmtime(-2**52) bug
http://code.google.com/p/y2038/source/detail?r=183

Modified:
/wiki/AmazingDiscoveries.wiki

=======================================
--- /wiki/AmazingDiscoveries.wiki Mon Nov 17 15:23:37 2008
+++ /wiki/AmazingDiscoveries.wiki Fri Feb 5 00:49:24 2010
@@ -11,6 +11,8 @@

Despite now using 64 bit CPUs (Intel Core Duo 2) still uses 32 bit
integers and time_t, presumably to avoid having 32 and 64 bit versions of
software. So it fails at the normal 32 bit boundries.

+10.6 appears to have fixed this, but a new bug emerges. gmtime(-2**52)
loses a day somewhere. BSD, DateTime.pm, Linux and y2038's own
implementation all agree its Mon Jan 25 20:11:44 -142711421 but OS X says
its Mon Jan 24th.
+