[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1406934677.8274.149.camel@eris.loria.fr>
Date: Sat, 02 Aug 2014 01:11:17 +0200
From: Jens Gustedt <jens.gustedt@...ia.fr>
To: musl@...ts.openwall.com
Subject: timespec_get
Hello,
here is an implementation of the missing timespec_get function. No big
deal as long as we restrict ourselves to the minimum, that is TIME_UTC
only.
The idea is that only calling the functions with the value TIME_UTC
has defined behavior, everything else is undefined. So this
implementation here doesn't make any assumption about the value of
TIME_UTC, and just makes the implementation depending choice of doing
the right thing, anyhow. Any other TIME values that might be added
later (by standard or by implementation) change the ABI, so nobody
could expect to be compatible.
Jens
--
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536 ::
:: :::::::::::::::::::::: gsm France : +33 651400183 ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
View attachment "timespec_get.patch" of type "text/x-patch" (908 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
