[RFC v2 03/20] y2038: linux: Provide __clock_settime64 implementation

[Lukasz Majewski]

Hi Florian,

> * Lukasz Majewski:
> 
> >> In my opinion, an existing 32-bit architecture which does not
> >> provide the clock_settime system call (that it has provided
> >> before) is just broken, and will be so at least until 2038.  
> >
> > Am I correct, that you opt for first option that glibc shall return
> > just -ENOSYS in that case?  
> 
> I think it's undefined.  For clock_settime, the only useful outcome is
> -1 with errno set to ENOSYS.  However, there are some system calls
> which cannot really fail (time, for instance), and there I would say
> that behavior is simply undefined.

Ok. I see. So the clock_settime syscall shall return from glibc with -1
and errno set to ENOSYS (I shall NOT try to set the time with
clock_settime64 bit syscall in this case).

Thanks for explanation, appreciated.

> 
> Thanks,
> Florian




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20190627/543c0888/attachment.sig>