summaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Make kvm(3) aware of ki_jid field.pjd2005-03-201-1/+17
| | | | | Reviewed by: gad MFC after: 3 days
* Use the correct values for softfloat, in both the little endian and the bigcognet2005-03-202-8/+13
| | | | endian cases.
* Fix the double rounding problem with subnormals, anddas2005-03-182-16/+36
| | | | remove the XXX comments, which no longer apply.
* Add missing prototypes for fma() and fmaf(), and remove an inaccuratedas2005-03-181-1/+2
| | | | comment.
* Make the fenv.h routines work for programs that use SSE fordas2005-03-172-85/+262
| | | | | | | | | | | | | | | | | | | | | | | | | floating-point arithmetic on i386. Now I'm going to make excuses for why this code is kinda scary: - To avoid breaking the ABI with 5.3-RELEASE, we can't change sizeof(fenv_t). I stuck the saved mxcsr in some discontiguous reserved bits in the existing structure. - Attempting to access the mxcsr on older processors results in an illegal instruction exception, so support for SSE must be detected at runtime. (The extra baggage is optimized away if either the application or libm is compiled with -msse{,2}.) I didn't run tests to ensure that this doesn't SIGILL on older 486's lacking the cpuid instruction or on other processors lacking SSE. Results from running the fenv regression test on these processors would be appreciated. (You'll need to compile the test with -DNO_STRICT_DFL_ENV.) If you have an 80386, or if your processor supports SSE but the kernel didn't enable it, then you're probably out of luck. Also, I un-inlined some of the functions that grew larger as a result of this change, moving them from fenv.h to fenv.c.
* Fix typo in comments (spell Linux correctly)emax2005-03-171-1/+1
| | | | | Submitted by: Markus Brueffer < markus at brueffer dot de > MFC after: 3 days
* Regenerate for 9.3.1dougb2005-03-175-6/+12
|
* bmake changes to handle the move of dns/sec and related filesdougb2005-03-172-17/+17
|
* Spell 'fedisableexcept' correctly.das2005-03-161-1/+1
|
* Document feenableexcept(), fedisableexcept(), and fegetexcept().das2005-03-162-1/+101
|
* Replace fegetmask() and fesetmask() with feenableexcept(),das2005-03-1610-57/+166
| | | | | | | | | | fedisableexcept(), and fegetexcept(). These two sets of routines provide the same functionality. I implemented the former as an undocumented internal interface to make the regression test easier to write. However, fe(enable|disable|get)except() is already part of glibc, and I would like to avoid gratuitous differences. The only major flaw in the glibc API is that there's no good way to report errors on processors that don't support all the unmasked exceptions.
* Remove fpsetsticky(). This was added for SysV compatibility, but duedas2005-03-159-162/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to mistakes from day 1, it has always had semantics inconsistent with SVR4 and its successors. In particular, given argument M: - On Solaris and FreeBSD/{alpha,sparc64}, it clobbers the old flags and *sets* the new flag word to M. (NetBSD, too?) - On FreeBSD/{amd64,i386}, it *clears* the flags that are specified in M and leaves the remaining flags unchanged (modulo a small bug on amd64.) - On FreeBSD/ia64, it is not implemented. There is no way to fix fpsetsticky() to DTRT for both old FreeBSD apps and apps ported from other operating systems, so the best approach seems to be to kill the function and fix any apps that break. I couldn't find any ports that use it, and any such ports would already be broken on FreeBSD/ia64 and Linux anyway. By the way, the routine has always been undocumented in FreeBSD, except for an MLINK to a manpage that doesn't describe it. This manpage has stated since 5.3-RELEASE that the functions it describes are deprecated, so that must mean that functions that it is *supposed* to describe but doesn't are even *more* deprecated. ;-) Note that fpresetsticky() has been retained on FreeBSD/i386. As far as I can tell, no other operating systems or ports of FreeBSD implement it, so there's nothing for it to be inconsistent with. PR: 75862 Suggested by: bde
* Dike out unwarranted reference to si_udev.phk2005-03-151-0/+4
|
* Finish repo-copy of lib/libbsnmp/modules to usr.sbin/bsnmpd/modules.harti2005-03-1414-3255/+1
| | | | | These modules are modules for the daemon, not for the library so they should be where the daemon is.
* Support extracting entries with pathnames longer than PATH_MAX. Inkientzle2005-03-134-27/+104
| | | | | testing, I've archived and restored dir trees with ~1MB pathnames. Most formats, of course, have much smaller limits.
* When rejecting rediculously large pax attributes (such as pathnameskientzle2005-03-131-2/+5
| | | | | over 1MB), issue a warning instead of forcing an internal assertion failure.
* Correctly pass low-level I/O errors back up to the caller whenkientzle2005-03-131-1/+4
| | | | reading cpio format.
* Better error messages on read and file-open errors.kientzle2005-03-132-6/+30
|
* Include detailed error message from zlib after a decompression error.kientzle2005-03-131-0/+3
|
* If the output is not a regular file, it's okay to add it to the archive.kientzle2005-03-132-4/+18
| | | | | | In particular, /dev/st0 can be added to an archive being written to /dev/st0. Thanks to: Jaakko Heinonen
* Use socklen_t where appropriate.stefanf2005-03-111-2/+2
|
* Avoid pointer arithmetics on void *.stefanf2005-03-101-1/+1
| | | | Approved by: alfred
* Remove an superfluous assignment.stefanf2005-03-101-1/+0
| | | | Approved by: alfred
* Use socklen_t where appropriate.stefanf2005-03-102-2/+3
| | | | Approved by: alfred
* In light of the recent 2^69 operation collision-finding attack on SHA1,cperciva2005-03-095-6/+522
| | | | | | | | add support for SHA256. Tested on: i386, sparc64 Tested using: NIST test vectors, built-in tests X-MFC-after: 5.4-RELEASE
* The third parameter to SHA_Update and SHA1_Update is a "size_t", not acperciva2005-03-091-2/+2
| | | | "unsigned int".
* Make MSG_NOSIGNAL available to native programs.alfred2005-03-091-5/+9
| | | | | | Bump FreeBSD_version to note this change. Reviewed by: sobomax
* Initialise `sn' before using its value.stefanf2005-03-081-2/+1
|
* Have ttyname_r() try to ask DEVFS for the device name.phk2005-03-082-35/+16
| | | | | | Document ttyname_r(). Simplify threaded/unthreaded stuff a lot.
* Make the returnvalue of times(3) insensitive to changes in wall-clock.phk2005-03-081-3/+5
| | | | PR: 78537
* Replace strong references with weak references. There's nodas2005-03-074-7/+7
| | | | | | | | particularly good reason to do this, except that __strong_reference does type checking, whereas __weak_reference does not. On Alpha, the compiler won't accept a 'long double' parameter in place of a 'double' parameter even thought the two types are identical.
* Remove an obsolete sentence from a comment.stefanf2005-03-071-2/+1
|
* Add korean NLS message catalogs for libcphantom2005-03-072-0/+498
| | | | | Submitted by: Hye-Shik Chang <perky@FreeBSD.org> PR: misc/78290
* - If z is 0, one of x or y is 0, and the other is infinite, raisedas2005-03-071-2/+18
| | | | | | | an invalid exception and return an NaN. - If a long double has 113 bits of precision, implement fma in terms of simple long double arithmetic instead of complicated double arithmetic. - If a long double is the same as a double, alias fma as fmal.
* Add manpage links for frexpf, frexpl, ldexpf, and ldexpl.das2005-03-071-0/+2
|
* Document frexpl and ldexpl.das2005-03-072-13/+25
|
* Document scalbnl and scalblnl.das2005-03-071-9/+16
|
* Document nextafterl and nexttoward{,f,l}.das2005-03-071-7/+21
|
* Add nexttoward to the list of implemented functions, and explicitlydas2005-03-071-4/+8
| | | | list the four that are still missing.
* Document fmal.das2005-03-071-16/+27
|
* Remove ldexp and ldexpf. The former is in libc, and the latter isdas2005-03-072-59/+0
| | | | | | identical to scalbnf, which is now aliased as ldexpf. Note that the old implementations made the mistake of setting errno and were the only libm routines to do so.
* - Remove s_ldexpf.c (now aliased to scalbn.)das2005-03-071-7/+12
| | | | | | | | | | | | | | | | | | | | | | - Add nexttoward{,f,l} and nextafterl. On all platforms, nexttowardl is an alias for nextafterl. - Add fmal. - Add man pages for new routines: fmal, nextafterl, nexttoward{,f,l}, scalb{,l}nl. Note that on platforms where long double is the same as double, we generally just alias the double versions of the routines, since doing so avoids extra work on the source code level and redundant code in the binary. In particular: ldbl53 ldbl64/113 fmal s_fma.c s_fmal.c ldexpl s_scalbn.c s_scalbnl.c nextafterl s_nextafter.c s_nextafterl.c nexttoward s_nextafter.c s_nexttoward.c nexttowardf s_nexttowardf.c s_nexttowardf.c nexttowardl s_nextafter.c s_nextafterl.c scalbnl s_scalbn.c s_scalbnl.c
* - Define FP_FAST_FMA for sparc64, since fma() is now implemented usingdas2005-03-071-4/+12
| | | | | | | sparc64's 128-bit long doubles. - Define FP_FAST_FMAL for ia64. - Prototypes for fmal, frexpl, ldexpl, nextafterl, nexttoward{,f,l}, scalblnl, and scalbnl.
* Alias scalbn as ldexpl and scalbnl on platforms where long double isdas2005-03-071-0/+8
| | | | the same as double.
* - Implement scalblnl.das2005-03-071-2/+34
| | | | | | - In scalbln and scalblnf, check the bounds of the second argument. This is probably unnecessary, but strictly speaking, we should report an error if someone tries to compute scalbln(x, INT_MAX + 1ll).
* Implement nexttowardf. This is used on both platforms with 11-bitdas2005-03-071-0/+60
| | | | exponents and platforms with 15-bit exponents for long doubles.
* Implement nexttoward and nextafterl; the latter is also known asdas2005-03-072-0/+155
| | | | | | | | | | | nexttowardl. These are not needed on machines where long doubles look like IEEE-754 doubles, so the implementation only supports the usual long double formats with 15-bit exponents. Anything bizarre, such as machines where floating-point and integer data have different endianness, will cause problems. This is the case with big endian ia64 according to libc/ia64/_fpmath.h. Please contact me if you managed to get a machine running this way.
* - Try harder to trick gcc into not optimizing away statementsdas2005-03-072-8/+19
| | | | | | that are intended to raise underflow and inexact exceptions. - On systems where long double is the same as double, nextafter should be aliased as nexttoward, nexttowardl, and nextafterl.
* - Define LDBL_NBIT to be a mask indicating the position of the integerdas2005-03-071-2/+10
| | | | | | | | | bit in a long double. For architectures that don't have such a bit, LDBL_NBIT is 0. This makes it possible to say `mantissa & ~LDBL_NBIT' in places that previously used an #ifdef to select the right expression. The optimizer should dispense with the extra arithmetic when LDBL_NBIT is 0 anyway. - Add an XXX comment for the big endian case.
* Define LDBL_NBIT to be a mask indicating the position of the integerdas2005-03-076-3/+9
| | | | | | | | bit in a long double. For architectures that don't have such a bit, LDBL_NBIT is 0. This makes it possible to say `mantissa & ~LDBL_NBIT' in places that previously used an #ifdef to select the right expression. The optimizer should dispense with the extra arithmetic when LDBL_NBIT is 0.
OpenPOWER on IntegriCloud