summaryrefslogtreecommitdiff
path: root/src/crypt
diff options
context:
space:
mode:
authorNatanael Copa <ncopa@alpinelinux.org>2015-08-13 17:28:39 +0200
committerRich Felker <dalias@aerifal.cx>2015-08-14 00:47:46 +0000
commitc13f2af1fe1856e36dd1b2773cac05d5d72641dc (patch)
tree4c37476636be82f48d057379699f896433f18d9e /src/crypt
parente5b086e1d5fe52bf1553357ee790de86eda27bf1 (diff)
downloadmusl-c13f2af1fe1856e36dd1b2773cac05d5d72641dc.tar.gz
musl-c13f2af1fe1856e36dd1b2773cac05d5d72641dc.tar.bz2
musl-c13f2af1fe1856e36dd1b2773cac05d5d72641dc.tar.xz
musl-c13f2af1fe1856e36dd1b2773cac05d5d72641dc.zip
match historical behavior for tm_gmtoff member of struct tm
tm_gmtoff is a nonstandard field, but on historical systems which have this field, it stores the offset of the local time zone from GMT or UTC. this is the opposite of the POSIX extern long timezone object and the offsets used in POSIX-form TZ strings, which represent the offset from local time to UTC. previously we were storing these negated offsets in tm_gmtoff too. programs which only used this field indirectly via strftime were not affected since strftime performed the negation for presentation. however, some programs and libraries accesse tm_gmtoff directly and were obtaining negated time zone offsets.
Diffstat (limited to 'src/crypt')
0 files changed, 0 insertions, 0 deletions