Re: mktime() problem when building print/a2ps

[Martin Husemann <martin%duskware.de@localhost>]

On Fri, Oct 14, 2022 at 09:13:19AM +0200, Thomas Klausner wrote:
> and this takes much longer! It's now been running ten minutes. That's
> longer than during the configure run. Perhaps it depends on interrupts
> or other things happening to stop?

There is a alarm(60) set to catch some strange broken mktime() implementations,
but what hits us here is that modern gcc seems to compile the for loop here:

  if ((time_t) -1 < 0)
    for (time_t_min = -1; (time_t) (time_t_min * 2) < 0; time_t_min *= 2)
      continue;

into an endless loop:

=> 0x400b77 <main+77>:  jmp    0x400b77 <main+77>

Our time_t is signed, so (time_t) -1 < 0 is true.

Didn't have coffee yet, right now I don't see why.

Martin