Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

time_t was almost certainly 64-bit on 64-bit archs from the beginning. There's just a lot of 32-bit stuff still out there. And here and there a disk format standarized before people started thinking about the end of time.


> time_t was almost certainly 64-bit on 64-bit archs from the beginning.

Not quite. Until recently llvm’s time_t was an alias to “long”. So a 32b value on 64b windows.


Any widely used disk format still uses 32-bit epoch?

Somehow I thought of FAT.. but UNIX epoch does not make so much sense...


Up to ext3 are using 32-bit timestamps. Ext4 now uses 34-bit, by extending only the upper range, and can cope with 7 * 2^32 seconds after the epoch, which is around 2446.

HFS+ uses a different 32-bit timestamp, which is unsigned and starts from 1904-01-01, so it expires on 2040.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: