RTEMS | Consider deprecating clock_get_tod Follow-up from "Cannot obtain dates later than 2100" (#5207)

[Chris Johns (@chris)]

Chris Johns commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5207#note_119630


There is no performance or resources issues with implementation `newlib` currently has. The code was changed to this algorithm in 2015 and the changes I made to fix the 2032 bug were done in 2014. When I reviewed the code in `newlib` it had a performance and resource profile that did not align to the RTEMS Classic API.

The issue with using `gmtime_t` inside an RTEMS published API is not knowing if it has change at a future point in time and and we do not know? Removing the call would help resolve the issue.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5207#note_119630
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/20250211/4817633b/attachment-0001.htm>