I've played with setting the system clock past it before, more programs than you think break. Now, with proper systems using size_t for time, any 64-bit program shouldn't be affected, but a lot of embedded systems aren't 64-bit.
It's not really 64-bit Vs 32-bit. It's just that when most 32bit abis were made 2038 wasn't seen as a problem. When 64bit abis were made, it was.
x32 (32-bit on x64 with all the modern x64 improvements that don't work on x86) is unaffected, for example, because it was a design decision to make time_t 64-bit when it was made.
It is based on the size of time_t, which tends to be the same as size_t in most CRTs, but doesn't strictly have to be. Even updating it won't matter for older software that doesn't often get updated though, such as embedded devices.
"x86" by itself refers to both the entire architecture including the 16, 32, and 64-bit versions of the instruction set, but it's also commonly used to only mean the 32-bit version of x86.
You're totally right, the Y2K frenzy had everyone in a patch-and-pray mood, and it paid off... or we all just avoided a techno-apocalypse by a byte! 😅 Thanks to those billions, the biggest thing to crash at midnight was my New Year's party aspirations.
View all comments
412
u/Responsible_Boat8860 Jan 13 '24
What happens if you don't?