RTEMS | rtems_clock_get_tod: Cannot obtain dates later than 2100 (#5143)
Joel Sherrill (@joel)
gitlab at rtems.org
Fri Nov 1 18:04:28 UTC 2024
Joel Sherrill created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5143
## Summary
The method rtems_clock_get_tod() uses its own math to fill in the rtems_time_of_day structure. Its calculations should be replaced with a call to gmtime() which can handle leap years better. This will replace time/date math with a more robust implementation which likely handles edge cases better.
Review #4338 (rtems_clock_set(): Cannot set future dates later than approximately 2105) to ensure that the cases it cites are still ok.
### Pre-set options
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5143
You're receiving this email because of your account on gitlab.rtems.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20241101/a8a6eeb2/attachment.htm>
More information about the bugs
mailing list