2038 problem time_t is 31 bits (signed) computers are expected to become super-ubiquitous, making it harder to track or find problematic systems newer filesystems - e.g. ext4, use 34-bits for time IOT / many devices - this is not just going to affect the larger machines / desktops and servers. it is in *all the things* Good description of problem and how to work on it: https://kernelnewbies.org/y2038 For the time-being, *use* time_t and to expect an ABI break down the road. If you get clever, you're making things more difficult for future generations. Coverity may be looking into the static analysis component of this. GPL violations play into this because the sources are unavailable - i.e., no way to rebuild. Q: If you are designing a new on-disk format, you *should* be considering longer timestamps.