On 28/06/16 10:07, Yury Norov wrote: > This is not about 64-bit time_t. This is about new type __ktime_t that > can replace time_t where it's safe. > there is no need to introduce new type names see the __WORDSIZE_TIME64_COMPAT32 case.