summaryrefslogtreecommitdiffstats
path: root/lib/libc
Commit message (Collapse)AuthorAgeFilesLines
* Add cross-reference to ftw(3).tjr2004-08-291-0/+1
|
* Remove the misleading description of the 'key' argument toroam2004-08-271-17/+1
| | | | | | | | | mpool_open(3) - it is *not* really used for synchronization; in fact, it is not used at all. PR: 70929 Submitted by: Martin Kammerhofer <dada@sbox.tugraz.at> MFC after: 3 days
* Don't forget to va_end() the va_list we get from va_copy().des2004-08-262-0/+2
| | | | | Submitted by: Sean McNeil <sean@mcneil.com> MFC after: 3 days
* Make profiling actually work. The gcc compiler emits a call to themarcel2004-08-252-4/+79
| | | | | | | | | | | | | _mcount() stub when profiling is enabled. Emit this code sequence for assembly routines as welli (MCOUNT definition in <machine/asm.h>. We do not pass the GOT entry however as the 4th argument, because it's not used. The _mcount() stub calls __mcount(), which does the actual work. Define _MCOUNT_DECL to define __mcount. We do not have an implementation of mcount(), so we define MCOUNT as empty, but have a weak alias to _mcount() in _mcount.S. Note that the _mcount() stub in the kernel is slightly different from the stub in userland. This is because we do not have to worry about nested routines in the kernel.
* note that it is the caller's responsibility to free any buffer passedalfred2004-08-241-0/+5
| | | | to setvbuf(3) and friends.
* Replace the current implementations of ftw() and nftw() with the OpenBSDtjr2004-08-243-193/+208
| | | | | implementations written by Todd C. Miller. These are cleaner, less buggy and actively maintained.
* 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)
* Make sure we allocate at least enough space for the TCB for variant I TLS.dfr2004-08-231-0/+2
| | | | MFC after: 3 days
* Update documentation to match reality: glob() sorts its result accordingtjr2004-08-231-4/+4
| | | | | | | to the current LC_COLLATE setting, not in "ASCII order". PR: 54391 MFC after: 1 week
* Re-word warning about the UTF2 encoding, taking care to use the wordtjr2004-08-211-3/+3
| | | | "obsolete" instead of "deprecated".
* Bump document date for previous.tjr2004-08-212-2/+2
|
* Re-word warning about the rune interface, taking care to use the wordtjr2004-08-212-12/+10
| | | | "obsolete" instead of "deprecated".
* Change "deprecated" in link-time warnings about various rune functionstjr2004-08-214-8/+8
| | | | to "obsolete".
* Re-word compatibility section, taking care to use the word "obsolete" totjr2004-08-2114-54/+64
| | | | | describe the 4.4BSD extension of accepting characters (runes) outside of the range of unsigned char.
* Reword recent addition about memory moving.alfred2004-08-191-5/+4
| | | | | | | | Requested by: keramida Bump .Dd Requested by: ru
* Clarify that realloc and reallocf may move the memory allocation.alfred2004-08-181-3/+7
|
* Always allocate a TLS area even if its empty - libpthread relies ondfr2004-08-181-7/+4
| | | | | | having a valid %gs when it initialises. MFC after: 2 days
* /me kicks cvs updatetrhodes2004-08-171-7/+1
| | | | | | | Revert previous commit, tjr already fixed it and I was too stupid to notice this fact. Approved by: re (to avoid failing cvs ci)
* Fix incorrect code in an example. The previous example would producetrhodes2004-08-171-2/+8
| | | | | | | | | | 19 column positions wide in the first line and 20 in the rest of the lines. This fixes the example to provide the correct output. PR: 53454 Noticed by: Kuang-che Wu <kcwu@kcwu.homeip.net> Submitted by: Marc Silver <marcs@draenor.org> Approved by: re (scottl)
* Fix alpha build and add __FBSDID.dfr2004-08-161-1/+4
| | | | PR: 70518
* Add support for TLS in statically linked programs.dfr2004-08-1514-8/+473
|
* Avoid using void pointers in additive expressions.stefanf2004-08-141-1/+1
| | | | PR: 56653
* Avoid using void pointers in additive expressions.stefanf2004-08-132-2/+2
| | | | | PR: 56653 (libc/rpc bits) Approved by: alfred
* Document the MNT_SNAPSHOT mount flag with a cross-referenceroam2004-08-131-1/+7
| | | | | | | to mksnap_ffs(8). PR: 70402 Submitted by: James Raftery <james@now.ie>
* Fix example.tjr2004-08-121-4/+5
|
* Implement wcwidth() as an inline function.tjr2004-08-121-11/+2
|
* Update "documentation date" fields.green2004-08-101-1/+1
|
* Update mlock(2) manpage to cross-reference m{,un}lockall(2), removegreen2004-08-101-1/+5
| | | | | a case where ENOMEM could be returned by munlock(2), and add possible system deadlock to the BUGS section.
* Fix an off-by-one bug that caused the first character of the buffer totjr2004-08-061-2/+1
| | | | be uninitialized.
* Bump the document date, since the content changed today.roam2004-08-063-3/+3
| | | | Discussed with: ru
* Fix a case of _SC_CLK_TCK being misspelled as _SC_CLOCK_TCK.roam2004-08-061-1/+1
| | | | | | PR: 69428 Submitted by: Sascha Schneider <suntsu@suntsu.org> MFC after: 2 weeks
* Cross-reference getnameinfo(3), getaddrinfo(3), getipnodebyname(3) androam2004-08-063-0/+4
| | | | | | | | getipnodebyaddr(3). PR: 54229 Submitted by: Samuel Tardieu <sam@inf.enst.fr> MFC after: 2 weeks
* Add stubs for TLS functions. These will be replaced at runtime by thedfr2004-08-032-3/+73
| | | | functional versions in rtld.
* Remove an implicit int parameter by using prototypes.stefanf2004-08-021-9/+3
|
* Don't pass function pointers via a void * parameter.stefanf2004-08-021-4/+4
|
* 1. Use correct alignment mask, -15 != ~15davidxu2004-07-311-2/+2
| | | | 2. Make end of frames
* Use #include <unistd.h> rather than the explicit externs in theimp2004-07-311-2/+1
| | | | | | example. The externs haven't been needed in about 10 years, so there's no reason to have them other than for hysterical raisins. And the California Rasins haven't been around for a long time...
* Re-word the COMPATIBILITY section, taking care to use the word "deprecated"tjr2004-07-2912-98/+74
| | | | | | to describe the 4.4BSD extension of accepting arguments outside the range of unsigned char. This gives us freedom to remove this extension when we remove the <rune.h> interface in FreeBSD 6.
* Use newly added __used attribute to keep static function symbols from beingkan2004-07-291-8/+8
| | | | eliminated by compiler optimizer.
* Remove unnecessary #include directives.tjr2004-07-293-8/+0
|
* Prefer <runetype.h> to <rune.h>, since the latter is going away soon.tjr2004-07-295-5/+5
|
* Remove useless checks for characters longer than INT_MAX bytes.tjr2004-07-293-12/+0
|
* Add support for multibyte characters.tjr2004-07-291-30/+84
|
* Add a paragraph break in the STANDARDS section to improve readability.tjr2004-07-291-0/+1
|
* Add support for multibyte characters.tjr2004-07-291-49/+112
|
* Document incorrect handling of multibyte characters due to limitationstjr2004-07-281-1/+6
| | | | of sh(1).
* Set fpu context flags to known values, zero is illegal.davidxu2004-07-281-0/+2
|
* ANSIfy and constify; this now builds with GCC 3.4.des2004-07-281-22/+19
|
* s/round/fpround/ to avoid naming clash with GCC builtin function.kan2004-07-281-8/+8
|
* Add UTF-8-specific implementations of mbsnrtowcs() and wcsnrtombs().tjr2004-07-271-0/+163
| | | | | | These convert plain ASCII characters in-line, making them only slightly slower than the single-byte ("NONE" encoding) version when processing ASCII strings.
OpenPOWER on IntegriCloud