time() and friends have Y2038 problem on 64 Windows

Description

I travelled 15 years into the future, and run the following code:

<?php
var_dump(time());

Resulted in this output:

int(-2081770632)

But I expected this output instead:

int(2213196664)

The problem is

https://github.com/php/php-src/blob/3d9a0a0c17c1660116c0699e6be734817d616292/win32/time.c#L46

Casting to long is appropriate since the declaration of struct timeval in WinSock2.h is:

struct timeval {
        long    tv_sec;         /* seconds */
        long    tv_usec;        /* and microseconds */
};

However, long is a 32bit value on LLP64 architectures.

One may argue that time travel is not supportable, but maybe we should heed the POSIX 7 advise:

Applications should use the clock_gettime() function instead of the obsolescent gettimeofday() function.

gettimeofday() has been removed from POSIX 8 altogether.

PHP Version

any

Operating System

Windows

Comienza en win32/time.c, alrededor de la línea enlazada donde time() obtiene y convierte tv_sec, y luego revisa la limitación de Windows LLP64 descrita en el informe y las time APIs relacionadas. Confirma el comportamiento en Windows de 64 bits y define la finalización como devolver una marca de tiempo positiva correcta posterior a 2038 sin el desbordamiento actual de 32 bits.