summaryrefslogtreecommitdiffstats
path: root/lib/libc
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Add an nftw(3) link.tjr2004-07-251-0/+1
|
* Remove unused variable.das2004-07-231-9/+1
| | | | Noticed by: Todd Miller <Todd.Miller@courtesan.com>
* Return the correct value when dst == NULL and conversion has stopped aftertjr2004-07-221-2/+2
| | | | nwc dropping to zero.
* now e.f.f.3.ip6.arpa is delegated, we no longer need to query ip6.intume2004-07-212-7/+1
| | | | Obtained from: KAME
* Read directly from the stdio buffer using the new __mbsnrtowcs() interfacetjr2004-07-211-14/+38
| | | | instead of making repeated calls to __fgetwc().
* Implement the GNU extensions of mbsnrtowcs() and wcsnrtombs(). These aretjr2004-07-2114-165/+317
| | | | | | | convenient when the source string isn't null-terminated. Implement the other conversion functions (mbstowcs(), mbsrtowcs(), wcstombs(), wcsrtombs()) in terms of these new functions.
* Use __wcsrtombs() and __sfvwrite() to convert and write the wide charactertjr2004-07-211-8/+25
| | | | string instead of multiple calls to __fputwc().
* Back out previous commit. Even though statfs(2) can take a regularcsjp2004-07-201-0/+4
| | | | | | | | file as an argument, it may still fail for the same reasons that open(2) can. Pointed out by: Jilles Tjoelker Apporived by: bmilekic (mentor)
* Remove reference to ENOTDIR in the documented errorscsjp2004-07-201-4/+0
| | | | | | | | for statfs(2). This is false, if the pathname specified is a regular file, then the information for the file system that the file lives on will be returned. Approved by: bmilekic (mentor)
* Call __mbrtowc() and __wcrtomb() directly instead of taking detourstjr2004-07-203-3/+6
| | | | through mbrtowc() and wcrtomb().
* Fix printing of long doubles to match the size thatgallatin2004-07-192-11/+8
| | | | | | | | | | | | | gcc is using. This fixes devstat consumers (like vmstat, iostat, systat) so they don't print crazy zillion digit numbers for disk transfers and bandwidth. According to gcc, long doubles are 64-bits, rather than 128 bits like the SVR4 ABI spec wants them to be.. Note that MacOSX also treats long doubles as 64-bits, and not 128 bits, so we are in good company. Reviewed by: das Approved by: grehan
* Add signalcontext, required by KSE.grehan2004-07-192-1/+104
|
* The new program counter should go into the trapframe's srr0 andgrehan2004-07-191-1/+1
| | | | not the link register, which was lucky enough to work.
* Update paths to reg*.c and regex2.h. Add a target to build regex.h.tjr2004-07-191-1/+3
|
* Update for removal of cclass.h. Trim some useless targets. Invoke mkhtjr2004-07-191-34/+6
| | | | with "sh mkh" so it works if the script is not executable.
* Update for recent changes to struct re_guts. Disable printing the contentstjr2004-07-191-38/+5
| | | | of OANYOF sets for the moment.
* Remove unused files.tjr2004-07-192-12/+0
|
* Make FLT_ROUNDS correctly reflect the dynamic rounding mode.das2004-07-196-3/+80
|
* Fix two bugs in the signbit() macro, which was implemented last year:das2004-07-193-100/+2
| | | | | | | | - It was added to libc instead of libm. Hopefully no programs rely on this mistake. - It didn't work properly on large long doubles because its argument was converted to type double, resulting in undefined behavior.
* Replace seven nominally MD implementations of frexp() that are brokendas2004-07-1816-456/+65
| | | | for subnormals with one implementation that works.
* Remove claim of conformance to IEEE Std. 1003.2. Replace it with a listtjr2004-07-181-7/+12
| | | | | | | of features required by the standard that the current implementation does not support. PR: 57911 (related)
* Remove claim of conformance to IEEE Std. 1003.2. Replace it with a listtjr2004-07-181-3/+7
| | | | | | | of features required by the standard that the current implementation does not support. PR: 57911
* Fix typo: carat -> caret.tjr2004-07-171-1/+1
|
* Document the MSG_DONTWAIT flag.harti2004-07-161-1/+8
|
* Add a cross reference to fgetwln(3).tjr2004-07-161-0/+1
|
* Add fgetwln(), a wide character version of fgetln().tjr2004-07-163-2/+192
|
* Rename slbexpand() to __slbexpand() and make it available outsidetjr2004-07-162-4/+5
| | | | of fgetln.c (non-static).
* Clarify getfsstat(2) usage.alfred2004-07-161-1/+6
| | | | | | | | | The getfsstat(2) function expects a buffer and a count, and returns a count. The confusing part is that the count it takes is a byte count, while the return value is a count of the number of structures it has filled out. Spell this out.
* Remove an entry from the BUGS section: we have multibyte charactertjr2004-07-121-2/+0
| | | | support now.
* Make regular expression matching aware of multibyte characters. The generaltjr2004-07-125-324/+478
| | | | | | | | | | | | | | | | | idea is that we perform multibyte->wide character conversion while parsing and compiling, then convert byte sequences to wide characters when they're needed for comparison and stepping through the string during execution. As with tr(1), the main complication is to efficiently represent sets of characters in bracket expressions. The old bitmap representation is replaced by a bitmap for the first 256 characters combined with a vector of individual wide characters, a vector of character ranges (for [A-Z] etc.), and a vector of character classes (for [[:alpha:]] etc.). One other point of interest is that although the Boyer-Moore algorithm had to be disabled in the general multibyte case, it is still enabled for UTF-8 because of its self-synchronizing nature. This greatly speeds up matching by reducing the number of multibyte conversions that need to be done.
* Add a new error code, REG_ILLSEQ, to indicate that a regular expressiontjr2004-07-122-1/+5
| | | | contains an illegal multibyte character sequence.
* Document the new PT_LWPINFO request. In fact, the request is so newmarcel2004-07-121-0/+19
| | | | | it hasn't even been implemented yet. I just wanted to be the first to try a new approach to development ;-)
* Remove incomplete support for multi-character collating elements. Removetjr2004-07-112-262/+8
| | | | unused character category calculations.
* Unbreak alpha: On alpha a long double is the same as a double andmarcel2004-07-101-0/+4
| | | | | | consequently the exponent is only 11 bits. Testing whether the exponent equals 32767 in that case only effects to compiler warnings and thus build breakage.
* Add fast paths for conversion of plain ASCII characters.tjr2004-07-091-0/+13
|
* Slightly reorganize and simplify.tjr2004-07-091-24/+11
|
* Bump document date for recent changes.das2004-07-091-1/+1
| | | | Prodded by: ru
* Document these functions as being in libm, not libc. Some of themdas2004-07-091-4/+1
| | | | | | | *are* in libc for historical reasons, but programmers should not rely on that fact. Also remove a BUGS section that is not relevant here.
* Implement the classification macros isfinite(), isinf(), isnan(), anddas2004-07-0917-501/+141
| | | | | | | | | | | | | | | | | | | | | isnormal() the hard way, rather than relying on fpclassify(). This is a lose in the sense that we need a total of 12 functions, but it is necessary for binary compatibility because we have never bumped libm's major version number. In particular, isinf(), isnan(), and isnanf() were BSD libc functions before they were C99 macros, so we can't reimplement them in terms of fpclassify() without adding a dependency on libc.so.5. I have tried to arrange things so that programs that could be compiled in FreeBSD 4.X will generate the same external references when compiled in 5.X. At the same time, the new macros should remain C99-compliant. The isinf() and isnan() functions remain in libc for historical reasons; however, I have moved the functions that implement the macros isfinite() and isnormal() to libm where they belong. Moreover, half a dozen MD versions of isinf() and isnan() have been replaced with MI versions that work equally well. Prodded by: kris
* Eliminate some magic numbers and correct description of _PC_NO_TRUNC.wollman2004-07-082-20/+45
| | | | | Slight emendation to _PC_CHOWN_RESTRICTED, which is in a very similar boat.
* Add a function to iterate over all characters in a particular charactertjr2004-07-083-2/+150
| | | | | | class. This is necessary in order to implement tr(1) efficiently in multibyte locales, since the brute force method of finding all characters in a class is infeasible with a 32-bit (or wider) wchar_t.
* there's no such define as KERN_NAME_MAX, change to _POSIX_NAME_MAX.alfred2004-07-071-1/+1
|
* Markup nits.ru2004-07-071-2/+4
|
* Fixed markup.ru2004-07-071-16/+22
|
* mdoc(7) fixes.ru2004-07-071-2/+3
|
* Move the return value information about the getenv(3) library functionhmp2004-07-061-4/+10
| | | | | | | | | under the RETURN VALUES section so it is consistent with others. Cleanup the return value text for getenv(3) a little while I am here. PR: docs/58033 MFC after: 3 days
* Keep it sync with OpenBSD:ache2004-07-061-3/+4
| | | | | | | An optional argument cannot start with '-', even if permutation is disabled. Obtained from: OpenBSD getopt_long.c v1.17
* Document incorrect handling of multibyte characters.tjr2004-07-061-1/+3
|
OpenPOWER on IntegriCloud