summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdtime/localtime.c
Commit message (Collapse)AuthorAgeFilesLines
* Split the contributed code from libc/stdtime from lib/libc/stdtimeedwin2010-02-261-2249/+0
| | | | to contrib/tzcode/stdtime.
* Use _pthread_once() rather than _once() for localtime() and gmtime(). Thesejhb2010-01-061-2/+2
| | | | | | | methods are only invoked when __isthreaded is true at which point it is safe to use _pthread_once() directly. MFC after: 1 week
* Use _once() to initialize the pthread key for thread-local storage to holdjhb2009-12-301-14/+14
| | | | | | the results of gmtime() instead of using a pthread mutex directly. MFC after: 1 week
* Use _once() to initialize the pthread key for thread-local storage to holdjhb2009-12-211-14/+14
| | | | | | the results of localtime() instead of using a pthread mutex directly. MFC after: 1 week
* Replace gmt_is_set and the gmt_mutex lock with a pthread_once_t variable andjhb2009-11-201-12/+13
| | | | | | an init routine run on the first invocation via _once(). MFC after: 1 week
* Improve the way failure of pthread_key_create() gets detected.edwin2009-09-141-2/+9
| | | | | | PR: threads/138603 Submitted by: Mikulas Patocka MFC after: 1 week
* Remove duplicate if-statement on gmt_is_set in gmtsub().edwin2009-06-231-8/+6
| | | | MFC after: 1 week
* MFV of tzcode2009e:edwin2009-05-231-180/+563
| | | | | | | | | | | | | | | | | | | | | | | | | Upgrade of the tzcode from 2004a to 2009e. Changes are numerous, but include... - New format of the output of zic, which supports both 32 and 64 bit time_t formats. - zdump on 64 bit platforms will actually produce some output instead of doing nothing for a looooooooong time. - linux_base-fX, with X >= at least 8, will work without problems related to the local time again. The original patch, based on the 2008e, has been running for a long time on both my laptop and desktop machine and have been tested by other people. After the installation of this code and the running of zic(8), you need to run tzsetup(8) again to install the new datafile. Approved by: wollman@ for usr.sbin/zic MFC after: 1 month
* Normally, we are often reading local time rather than setting time zone,davidxu2008-04-011-22/+63
| | | | | replace mutex with rwlock, this should eliminate lock contention in most cases.
* Reduce lock contention for simple cases.imp2007-12-191-16/+22
| | | | | | # this really should be done with pthread_once, but I've debugged this code. Reviewed by: arch@
* On FreeBSD/arm, any value > 50 bits will result in a rediculously hugeimp2007-01-191-2/+2
| | | | | | | | | | | number being returned for mktime and timegm calls. Choose 48 because that works well. This does reduce the dynamic range of tm_year from about 2 billion years down to "only" about 9 million years. Please contact me if this restriction poses a problem. Due to the complexity of the code, I admit that I didn't trace down what, exactly, was overflowing with longer bits. This fixes software that we run on the embedded systems we have.
* struct tm.tm_year is listed as 'years since 1900', and is signed. Onpeter2004-08-241-0/+3
| | | | | | | | | | | | | | | | | | | | | 64 bit systems, years roughly -2^31 through 2^31 can be represented in time_t without any trouble. 32 bit time_t systems only range from roughly 1902 through 2038. As a consequence, none of the date munging code for all the various calendar tweaks before then is present. There are other problems including the fact that there was no 'year zero' and so on. So rather than get excited about trying to figure out when the calendar jumped by two weeks etc, simply disallow negative (ie: prior to 1900) years. This happens to have an important side effect. If you bzero a 'struct tm', it corresponds to 'Jan 0, 1900, 00:00 GMT'. This happens to be representable (after canonification) in 64 bit time_t space. Zero tm structs are generally an error and mktime normally returns -1 for them. Interestingly, it tries to canonify the 'jan 0' to 'dec 31, 1899', ie: year -1. This conveniently trips the negative year test above, which means we can trivially detect the null 'tm' struct. This actually tripped up code at work. :-/ (Don't ask)
* Merge changes from the tzcode2004a import. Wherever possible I tried to bringstefanf2004-06-141-52/+116
| | | | | | us closer to the vendor branch. Requested by: wollman
* Change defualt time zone from GMT to UTC. This will not be MFC-ed, andkensmith2004-06-111-1/+6
| | | | was done before 5-STABLE on purpose...
* Remove a couple of casts added for an ancient Sun compiler.stefanf2004-06-081-11/+2
| | | | Approved by: das (mentor)
* Eliminate 61 warnings emitted at WARNS=2 (leaving 53 to go).nectar2003-02-161-2/+2
| | | | | | | Only warnings that could be fixed without changing the generated object code and without restructuring the source code have been handled. Reviewed by: /sbin/md5
* Do not guarantee an overflow of tm_year when doing the binary search inpeter2002-12-051-0/+6
| | | | | | localtime/mktime/tmcomp and friends on ia64. Approved by: re
* Replace rev 1.33 with a real fix. The problem was integer overflowspeter2002-12-021-8/+2
| | | | | | | | | | | | | | | | when trying to store the year in a signed int. The maximum time_t on ia64 is around 292 billion years in the future, but 'int' and struct tm.tm_year can only represent then ext 2.1 billion years or so. This solves the problem of mktime/localtime looping on ia64. Unfortunately, the standards say that tm_year is an 'int', so we are still stuck with a y2147483647 bug. bash2's configure script looks for bugs in mktime() and fails on ia64 because of this. However, mktime() on FreeBSD fails the test normally anyway so this is no big loss. This change does not affect any other platforms besides ia64. Approved by: re
* Fix a nasty bug exposed by mktime() when time_t is significantly biggerpeter2002-09-031-0/+6
| | | | | | | than 32 bits. It was trying to figure out things like the day of week of when time_t is roughly 2^62 etc. Make a better guess for the starting point for the binary search that works on both 32 and 64 bit types. I have been using this for a while now.
* Remove use of __P() (actually P()) from code now that it's no longeralfred2002-05-281-38/+38
| | | | available.
* Fix fd leak. Threads people: does the call above to `access' need to bewollman2002-05-031-1/+3
| | | | | | | underscored as well? PR: 37717 Submitted by: fred@clift.org (slightly modified by me)
* Fix the style of the SCM ID's.obrien2002-03-221-2/+2
| | | | I believe have made all of libc .c's as consistent as possible.
* Remove 'register' keyword.obrien2002-03-211-73/+73
|
* Don't mung the user's tm_sec field if we don't need to. (Belt-and-suspenderswollman2001-06-051-1/+3
| | | | | | | | | version.) PR: bin/27630 Submitted by: Arthur David Olson <ado@nci.nih.gov> Obtained from: Timezone mailing-list <tz@elsie.nci.nih.gov> MFC after: 1 month
* Don't depend on lcl_mutex being a recursive mutex.tegge2001-02-151-5/+5
| | | | Reviewed by: deischen
* Remove _THREAD_SAFE and make libc thread-safe by default bydeischen2001-01-241-108/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | adding (weak definitions to) stubs for some of the pthread functions. If the threads library is linked in, the real pthread functions will pulled in. Use the following convention for system calls wrapped by the threads library: __sys_foo - actual system call _foo - weak definition to __sys_foo foo - weak definition to __sys_foo Change all libc uses of system calls wrapped by the threads library from foo to _foo. In order to define the prototypes for _foo(), we introduce namespace.h and un-namespace.h (suggested by bde). All files that need to reference these system calls, should include namespace.h before any standard includes, then include un-namespace.h after the standard includes and before any local includes. <db.h> is an exception and shouldn't be included in between namespace.h and un-namespace.h namespace.h will define foo to _foo, and un-namespace.h will undefine foo. Try to eliminate some of the recursive calls to MT-safe functions in libc/stdio in preparation for adding a mutex to FILE. We have recursive mutexes, but would like to avoid using them if possible. Remove uneeded includes of <errno.h> from a few files. Add $FreeBSD$ to a few files in order to pass commitprep. Approved by: -arch
* Temporary cosmetic change to prevent gcc-2.95.2 from doing ancracauer2000-03-081-1/+1
| | | | | | | | | | | | | optimization that generates code our current as doesn't understand. The result is bad code that damages dynamic symbol locations at runtime. Ouch. See PR bin/16862 and discussion in -current. This change will be backed out when gcc and gas are back in sync. PR: Fixes bin/16862, but not the underlying problem. Submitted by: bde Approved by: jdk
* Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(),jasone2000-01-271-3/+3
| | | | | | | | | | | | | | | | | just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo(). Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo(). Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid(). Make thread cancellation fully POSIX-compliant. Suggested by: deischen
* Add three-tier symbol naming in support of POSIX thread cancellationjasone2000-01-121-3/+5
| | | | | | points. For library functions, the pattern is __sleep() <-- _libc_sleep() <-- sleep(). The arrows represent weak aliases. For system calls, the pattern is _read() <-- _libc_read() <-- read().
* Merge from vendor branch: timezone file structure changes and doco.wollman1999-01-211-1/+1
| | | | | | Fix localtime.c to deal with new magic number field. Obtained from: ftp://elsie.nci.nih.gov/pub/tzcode1999a.tar.gz
* Make ctime_r, asctime_r, gmtime_r, and localtime_r available in libc.dt1999-01-041-6/+4
|
* Replace memory leaking instances of realloc with non-leaking reallocf.imp1998-09-161-2/+7
| | | | | | | | | | | In some cases replace if (a == null) a = malloc(x); else a = realloc(a, x); with simple reallocf(a, x). Per ANSI-C, this is guaranteed to be the same thing. I've been running these on my system here w/o ill effects for some time. However, the CTM-express is at part 6 of 34 for the CAM changes, so I've not been able to do a build world with the CAM in the tree with these changes. Shouldn't impact anything, but...
* Add a #ifdef _THREAD_SAFE around ctime_rphk1998-04-201-0/+2
|
* ctime_r and asctime_r are not implemented.phk1998-04-191-0/+9
| | | | | | | | prototypes in time.h do not match POSIX. PR: 6345 Reviewed by: phk Submitted by: Dmitry Khrustalev <dima@xyzzy.machaon.ru>
* Change in name of the static initializer define.jb1998-04-041-4/+4
|
* Submitted by: Jeremy Allison (jallison@whistle.com)julian1998-02-181-3/+5
| | | | | | fix a slight confusion about which draft of threads we are supporting. this allows something as big and ugly as samba to be compiled with libc_r and still work! our user-level pthreads seems amazingly robust!
* Back out 1.14 until I reproduce trouble reportsimp1997-03-251-4/+2
|
* Don't open the tz file if we're running setuid or setgid to prevent infomrationimp1997-03-241-2/+4
| | | | | | leakage. Submitted by: Julian Assange
* Submitted by: John Birrelljulian1997-02-051-5/+3
| | | | uthreads update from the author.
* When attempting to load a `lastditch' timezone (e.g., because the loadwollman1997-01-131-7/+8
| | | | | | | | | of the user's timezone failed), don't bail if the specified timezone doesn't have an offset; in this case it isn't going to. (Perhaps it would be better to change the caller to always supply one, but this is quick and clean and fixes the bug in the easiest possible way.) Should be in 2.2. Fixes (properly) PR#1740.
* Parameters for localtime_r() and gmtime_r() definitions changed.hsu1996-11-111-8/+8
| | | | | Parameters for pthread_getspecific() call changed. pthread_keycreate() renamed to pthread_key_create().
* Require that a timezone specified via the TZ envariable be a regularwollman1996-10-091-1/+7
| | | | | file (and not a directory or a device which might also be readable). Closes PR#1740.
* Submitted by: John Birrell <cimaxp1!jb@werple.net.au>julian1996-08-201-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Here are the diffs for libc_r to get it one step closer to P1003.1c These make most of the thread/mutex/condvar structures opaque to the user. There are three functions which have been renamed with _np suffixes because they are extensions to P1003.1c (I did them for JAVA, which needs to suspend/resume threads and also start threads suspended). I've created a new header (pthread_np.h) for the non-POSIX stuff. The egrep tags stuff in /usr/src/lib/libc_r/Makefile that I uncommented doesn't work. I think its best to delete it. I don't think libc_r needs tags anyway, 'cause most of the source is in libc which does have tags. also: Here's the first batch of man pages for the thread functions. The diff to /usr/src/lib/libc_r/Makefile removes some stuff that was inherited from /usr/src/lib/libc/Makefile that should only be done with libc. also: I should have sent this diff with the pthread(3) man page. It allows people to type make -DWANT_LIBC_R world to get libc_r built with the rest of the world. I put this in the pthread(3) man page. The default is still not to build libc_r. also: The diff attached adds a pthread(3) man page to /usr/src/share/man/man3. The idea is that without libc_r installed, this man page will give people enough info to know that they have to build libc_r.
* Merge the recently-imported tzcode96h distribution (libc portion). Thewollman1996-07-181-56/+59
| | | | | | part that does zic(8)/zdump(8) is still yet to be imported (but the old zic and zdump will work just fine with these header files and the data format has not changed).
* Removed false copyrights...scrappy1996-05-271-34/+0
|
* Added in appropriate Berkeley copyright and RCS Id: stringscrappy1996-05-271-0/+36
| | | | Closes PR#doc/536
* Reviewed by: julian and (hsu?)julian1996-01-221-1/+129
| | | | | | Submitted by: John Birrel(L?) changes for threadsafe operations
* The European Commission went out and invented a new sort of summer-timewollman1995-08-051-129/+211
| | | | | | changeover, so we have to extend the format of timezone files (in a backward- compatible way, of course). This probably means that libc needs a minor version number bump before 2.2 is released (or maybe not).
* Remove trailing whitespace.rgrimes1995-05-301-1/+1
|
* Port to FreeBSD. Not ready for inclusion in libc just yet, but herewollman1994-09-131-1/+1
| | | | so we can compile zic.
OpenPOWER on IntegriCloud