Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

32bit time and Year 2038 problem #101

Open
dram opened this issue Oct 26, 2016 · 1 comment
Open

32bit time and Year 2038 problem #101

dram opened this issue Oct 26, 2016 · 1 comment

Comments

@dram
Copy link
Contributor

dram commented Oct 26, 2016

While doing PR #100, I found that Self using 32bit time representation. As it will suffer from Year 2038 problem, I think it need to be fixed.

@dram dram changed the title 32bit time 32bit time and Year 2038 problem Oct 26, 2016
@dram
Copy link
Contributor Author

dram commented Oct 28, 2016

According to Wikipedia:

Linux uses a 64-bit time_t for 64-bit architectures only; the pure 32-bit ABI is not changed due to backward compatibility.

It seems that it's not easy to support 64-bit time in 32-bit Self, so maybe making Self support 64-bit system is the first to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant