On 12/31/21 04:56, Gisle Vanem wrote:
Paul Eggert wrote:
On 12/30/21 07:48, Gisle Vanem wrote:
-#elif defined HAVE_TIMESPEC_GETRES
+#elif defined HAVE_TIMESPEC_GETRES && HAVE_TIMESPEC_GETRES
This change has an effect only if there's the equivalent of '#define
HAVE_TIMESPEC_GETRES 0'
Paul Eggert wrote:
On 12/30/21 07:48, Gisle Vanem wrote:
-#elif defined HAVE_TIMESPEC_GETRES
+#elif defined HAVE_TIMESPEC_GETRES && HAVE_TIMESPEC_GETRES
This change has an effect only if there's the equivalent of '#define HAVE_TIMESPEC_GETRES 0' somewhere.
Since 'time.in.h' says:
# if
On 12/30/21 07:48, Gisle Vanem wrote:
-#elif defined HAVE_TIMESPEC_GETRES
+#elif defined HAVE_TIMESPEC_GETRES && HAVE_TIMESPEC_GETRES
This change has an effect only if there's the equivalent of '#define
HAVE_TIMESPEC_GETRES 0' somewhere. How did that happen? If your platform
lacks
Trying the new test 'test-timespec_getres.exe'
gave me a "Stack overflow - code c0fd (first chance)"
since in my case here on Windows/MSVC, the function really is:
long int gettime_res (void)
{
struct rpl_timespec res;
timespec_getres (, 1);
and then 'timespec_getres()' calls
