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

Gedare Bloom (@gedare) gitlab at rtems.org
Fri Feb 7 21:30:20 UTC 2025



Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5207

Assignee: Gedare Bloom

The following discussion from !339 should be addressed:

- [ ] @chris started a [discussion](https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/339#note_119256):  (+1 comment)

    > Does this change effect the performance of the call? The localized code was designed to be fast and simple. I suggest a review the newlib to make sure it is suitable for use in this RTEMS API call.
    > 
    > If newlib is solving this problem should this call remain present or should we depreciate it?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5207
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/20250207/19522cab/attachment.htm>


More information about the bugs mailing list