Comment 5 for bug 2055837

(In reply to Joseph Myers from comment #2)
> Shouldn't we fix how suseconds_t is defined in glibc in the 64-bit time
> case? It's not as if any interfaces in glibc use suseconds_t other than as
> part of struct timeval (though we should still warn in NEWS about potential
> compatibility issues for any interfaces using suseconds_t in third-party
> libraries).

That's why I am not fully sure which would be the best way, since this strictly is an ABI break.

At least using the timespec trick to keep the type as currently defined should not cause any issue (since the type holds all potential values), and it should be back-portable.