Introducing wc_time_t to override time_t #7170
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On some systems time_t is a 32bit signed int, triggering the y2038 issue. It's possible now to override time_t explicitly using a signed 64bit field, by defining TIME_T_OVERRIDE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Work in progress] 🧑🏭
Description
On some systems time_t is a 32bit signed int, triggering the y2038 issue.
It's possible now to override time_t explicitly using a signed 64bit field, by defining TIME_T_OVERRIDE
Fixes y2038 bug in systems with a broken time_t
Testing
Just via
make checkfor now, with the option on.Checklist