diff options
author | Zack Weinberg <zackw@panix.com> | 2019-09-04 16:51:23 +0000 |
---|---|---|
committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2019-10-30 17:11:10 -0300 |
commit | 2b5fea833bcd0f651579afd16ed7842770ecbae1 (patch) | |
tree | 1da4cec5abfb962a083d4c1b520a222f7ba5e30d /posix/bug-ga1.c | |
parent | f9a7554009cf38f390e74fcabc5b49f974f72382 (diff) | |
download | glibc-2b5fea833bcd0f651579afd16ed7842770ecbae1.tar.gz glibc-2b5fea833bcd0f651579afd16ed7842770ecbae1.tar.xz glibc-2b5fea833bcd0f651579afd16ed7842770ecbae1.zip |
Consolidate and deprecate ftime
ftime is an obsolete variation on gettimeofday, offering only millisecond time resolution; it was probably a system call in ooold versions of BSD Unix. For historic reasons, we had three implementations of it. These are all consolidated into time/ftime.c, and then the function is deprecated. For some reason, the implementation of ftime in terms of gettimeofday was rounding rather than truncating microseconds to milliseconds. In all the other places where we use a higher-resolution time function to implement a lower-resolution one, we truncate. ftime is changed to match, just for tidiness' sake. Like gettimeofday, ftime tries to report the time zone, and using that information is always a bug. This patch dummies out the reported timezone information; the timezone and dstflag fields of the returned "struct timeb" will always be zero. Checked on x86_64-linux-gnu, i686-linux-gnu, powerpc64le-linux-gnu, powerpc64-linux-gnu, and powerpc-linux-gnu. Co-authored-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Reviewed-by: Lukasz Majewski <lukma@denx.de>
Diffstat (limited to 'posix/bug-ga1.c')
0 files changed, 0 insertions, 0 deletions