Fifth draft of the Y2038 design document

[Joseph Myers]

On Wed, 22 Feb 2017, Albert ARIBAUD wrote:

> So the existing (32-bit time) public API symbol 'clock_gettime' has to
> remain for 32-bit time callers, and another one needs to be provided
> for 64-bit time callers -- that is the one which would be named
> 'clock_gettime64'.

But the API symbol for 64-bit callers is clock_gettime; such callers use 
_TIME_BITS=64.  There should be no API clock_gettime64 at all, without a 
clear usage case for calling such a function from code built with 
_TIME_BITS=32.

-- 
Joseph S. Myers
joseph@codesourcery.com