RTEMS | time_t assigned to uint32_t results in value truncation (#5737)
Joel Sherrill (@joel)
gitlab at rtems.org
Tue Sep 1 17:09:53 UTC 2026
Issue created by Joel Sherrill: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5737
## Summary
These "use of 32-bit time_t" defects is reported by Coverity. They appear to be cases where a variable of type _time_t_ is on the right hand side of an assignment and a variable of type _uint32_t_ is on the left hand side:
- [1512539](https://scan5.scan.coverity.com/#/project-view/29811/10069?selectedIssue=1512539) cpukit/libmisc/cpuuse/cpuusagetop.c:157
- [1512546](https://scan5.scan.coverity.com/#/project-view/29811/10069?selectedIssue=1512546) cpukit/score/src/schedulercbsreleasejob.c:60
- [1512551](https://scan5.scan.coverity.com/#/project-view/29811/10069?selectedIssue=1512551) bsps/shared/dev/getentropy/getentropy-cpucounter.c:74
## Steps to reproduce
Follow above links to the details.
<!-- Pre-set options
- milestone
-->
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/work_items/5737
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/5-9uc6igqe843melxezcszjklwx-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260901/82b10e92/attachment.htm>
More information about the bugs
mailing list