Year 2038 Issue

Year 2038 Issue

[Steger, Matthew]

What version (exactly) of GCC added the "time64_t" and all TIME Related functions (including Printing formats) allowed 64-bit time (to FIX the Year 2038 issue with "time_t")

Also did *ANY* version of GCC support 32-bit UNSIGNED time (good until 2106) including all TIME Related fucntions (and Printing formats)?

Matthew B. Steger | Sr. Software Engineer
T +1.847.871.1177 | M +1.630.254.2243

Genfare | 800 Arthur Ave | Elk Grove Village IL 60007

Genfare.com<https://www.genfare.com/> | LinkedIn<https://www.linkedin.com/company/genfare> | Customer Care<https://www.genfare.com/customer-care/>

The information contained in this electronic mail transmission is intended by SPX Corporation for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender's address records can be corrected.

Re: Year 2038 Issue

[Jonathan Wakely]

On Wed, 7 Jul 2021, 21:10 Steger, Matthew via Gcc-help, <
gcc-help@gcc.gnu.org> wrote:

> What version (exactly) of GCC added the "time64_t" and all TIME Related
> functions (including Printing formats) allowed 64-bit time (to FIX the Year
> 2038 issue with "time_t")
>

Those functions are not part of GCC. They are provided by the C library,
not GCC.

If you are using Linux, your C library is probably glibc. It is a
completely separate project from GCC with its own releases.


> Also did *ANY* version of GCC support 32-bit UNSIGNED time (good until
> 2106) including all TIME Related fucntions (and Printing formats)?
>

GCC supports whatever the C library does.