View Feed
group-icon
Coffee Room
Discuss anything here - everything that you wish to discuss with fellow engineers.
12796 Members
Join this group to post and comment.

Y2K38 Problem | Y2K Problem Was Old!

There's yet another big problem! Its Y2k38 Problem!!! Check this out, as this explains it all:
[​IMG]
Kaustubh Katdare
Kaustubh Katdare • Feb 6, 2012
Moved the post to a new thread. Boy! Is that a real problem?
The_Big_K
Moved the post to a new thread. Boy! Is that a real problem?
Whaaat??? How can you say??? Most of the processors have their clocks running in 32 Bit mode!!! 😲

PS: My 5000th Post! 😀
Tanu Pawar
Tanu Pawar • Feb 7, 2012
Seriously we are goona face big problem....if we continue to use 32 bit....so now a days
most operating systems designed to run on 64-bit hardware already use signed 64-bit time_t integers, effectively eliminating the Year 2038 problem in any software that has been developed to use the extended format.

Using a signed 64-bit value introduces a new wraparound date that is over twenty times greater than the theorized age of the universe: approximately 292 billion years from now, at 15:30:08 on Sunday, 4 December 292,277,026,596.
born_star16
born_star16 • Feb 7, 2012
Thank god, I have 64 bit processor. 😛
born_star16
Thank god, I have 64 bit processor. 😛
Boss, the time is given by a 32 bit application time_t!!! That is still 32 bit!!! 😲
Harshad Italiya
Harshad Italiya • Feb 7, 2012
Is there any solution for this problem?
Migrating to 64 Bit time_t...
born_star16
born_star16 • Feb 8, 2012
Praveen-Kumar
Boss, the time is given by a 32 bit application time_t!!! That is still 32 bit!!! 😲
Oh! missed again. Time to migrate. 😀
born_star16
Oh! missed again. Time to migrate. 😀
Ha ha!!! All the best!!! 😀 Soon!!! Just 26 years more!!! 😛

Share this content on your social channels -