summaryrefslogtreecommitdiffstats
path: root/lib/libc
Commit message (Collapse)AuthorAgeFilesLines
* Do not export 'end' symbol. It is not meant to be visible to outsidekan2007-05-161-1/+1
| | | | | world and it wreak havoc if libc collides with other versioned libraries.
* Document RFTHREADpav2007-05-141-1/+9
| | | | | | PR: docs/78915 Submitted by: Marc Olzheim <marcolz@stack.nl> MFC after: 1 week
* I guess powerpc needs vfork(), add it to the symbol list.deischen2007-05-141-0/+1
| | | | Submitted by: marius
* Add ether_aton_r and ether_ntoa_r to public symbol map for libc.rwatson2007-05-131-0/+2
| | | | Pointed out by: deischen
* Remove .mcount from gmon's Symbol map and add it to the appropriatedeischen2007-05-135-2/+27
| | | | | | | arch. It can be named differently depending on the arch (.mcount, _mcount). Submitted by: marius
* Enable symbol versioning by default. Use WITHOUT_SYMVER to disable it.deischen2007-05-131-2/+0
| | | | | | | | | | Warning, after symbol versioning is enabled, going back is not easy (use WITHOUT_SYMVER at your own risk). Change the default thread library to libthr. There most likely still needs to be a version bump for at least the thread libraries. If necessary, this will happen later.
* Add and document ether_ntoa_r() and ether_aton_r() functions, which acceptrwatson2007-05-132-37/+85
| | | | | | passed storage buffers rather than using static storage. Reimplement ether_ntoa() and ether_aton() in terms of these functions. These variants are thread-safe.
* Move to more conformant style(9) before making functional changes.rwatson2007-05-131-51/+35
|
* - Add bits for userland profiling. For sun4u this is compile-tested only.marius2007-05-111-0/+1
| | | | - Replace magic 14 with PIL_TICK.
* We should never zero-pad INF or NaN (yielding silly strings like "00inf")das2007-05-081-0/+1
| | | | even if the programmer asks for zero padding.
* Fix a rounding error.das2007-05-081-1/+1
| | | | Reported by: Bruno Haible
* - Fix typogabor2007-05-041-2/+2
| | | | | Approved by: keramida (mentor) MFC after: 3 days
* Back out all POSIXified *env() changes.ache2007-05-014-96/+41
| | | | | | | | | Not because I admit they are technically wrong and not because of bug reports (I receive nothing). But because I surprisingly meets so strong opposition and resistance so lost any desire to continue that. Anyone who interested in POSIX can dig out what changes and how through cvs diffs.
* Bump .Ddache2007-04-301-1/+1
| | | | Suggested by: Henrik Brix Andersen <henrik@brixandersen.dk>
* Add phraseache2007-04-301-1/+2
| | | | | "so altering the argument shall change the environment." into putenv description.
* Make putenv() fully conforms to Open Group specs Issue 6ache2007-04-304-26/+58
| | | | | | | | | | | (also IEEE Std 1003.1-2001) The specs explicitly says that altering passed string should change the environment, i.e. putenv() directly puts its arg into environment (unlike setenv() which just copies it there). It means that putenv() can't be implemented via setenv() (like we have before) at all. Putenv() value lives (allows modifying) up to the next putenv() or setenv() call.
* Remove special case skipping initial '=' of the setenv() value "forache2007-04-302-7/+0
| | | | | | | | | compatibility with the different environment conventions" (man page). With the standards, we don't have them different anymore and IEEE Std 1003.1-2001 says that "The values that the environment variables may be assigned are not restricted except that they are considered to end with a null byte"
* Make setenv, putenv, getenv and unsetenv conforming to Open Group specsache2007-04-304-19/+48
| | | | | | | | | Issue 6 (also IEEE Std 1003.1-2001) in following areas: args, return, errors. Putenv still needs rewriting because specs explicitly says that altering passed string later should change the environment (currently we copy the string so can't provide that).
* Add missing links and sort.pjd2007-04-291-3/+9
|
* Make sure FBSDprivate_1.0 is located at the end of the versionkan2007-04-291-1/+1
| | | | inheritance chain.
* Use C comments since we now preprocess these files with CPP.deischen2007-04-2930-166/+242
|
* Number the private version namespace in case we ever want to havedeischen2007-04-291-1/+1
| | | | compatibility between versions (as we do for the public namespace).
* Remove the MSG_PEEK flag from the documentation of the send(2) syscall -roam2007-04-271-1/+0
| | | | | | | | it is only relevant to receiving data from sockets, not to sending. PR: 109667 Submitted by: Jari Kirma <kirma@cs.hut.fi> Approved by: wollman
* Make inet6_rth_* family of functions more compliant with RFC3542:mtm2007-04-191-1/+9
| | | | | | | | | | | 1. CMSG_NXTHDR(mhdr, cmsg) is supposed to dereference cmsg and return the next header in the chain. If cmsg is NULL it should return the first header, behaving essentially like CMSG_FIRSTHDR(). 2. inet6_rth_(space|init|add) should do basic checking on their input to verify that the number of headers (segments) is between 0 and 127 inclusive. MFC-After: 1 month
* Grammer correction from: emastephk2007-04-191-1/+1
|
* Loosen return value spec for fputs to be standards compliant so peoplephk2007-04-191-5/+2
| | | | don't program against our more restrictive behaviour.
* Cleanup sysconf(3) a bit. sysconf(3) assumes in some places it operatespjd2007-04-141-21/+18
| | | | | | | | | | on int, but in fact it should operate on long. - Introduce 'lvalue' variable, which is long. - Fix _SC_XOPEN_SHM for 64bit archs. - Fix _SC_PHYS_PAGES for 64bit archs. Reported by: simokawa - Use lvalue for pathconf(3), as it returns long. - Cast value explicitly to long on return.
* Belatedly bump Dd for my recent changes.emaste2007-04-111-1/+1
|
* Expand the description of the host's UUID.ru2007-04-101-3/+3
| | | | OK'ed by: pjd
* Swap "underflow"/"overflow" in the table header.ru2007-04-101-2/+2
| | | | | Submitted by: Ricardo Nabinger Sanchez MFC after: 3 days
* Clean-ip TLS symbol versions. [_]__tls_get_addr function is part ofkan2007-04-092-6/+2
| | | | | | | the platform ABI and as such does not belong in FBSDprivate. __libc_tls_* functions do not have to be visible to outside world at all.
* Document KERN_HOSTUUID.pjd2007-04-091-1/+4
| | | | Reminded by: ru
* Document PT_GETNUMLWPS.emaste2007-04-091-0/+3
|
* Describe PT_GETLWPLIST's arguments.emaste2007-04-071-0/+9
|
* __p_rcode_syms is declared as external in resolv.conf, so it cannot bekan2007-04-062-1/+2
| | | | | | | | | | redeclared as static in res_debug.c. Make __p_rcode_syms global and add it to Symbol map. The rest of __p_??_syms are already global. Choice of FBSD_1.0 version for these debug symbols seems strange and should be revisited before symbol versioning is enabled for libc.so.7.
* Bump date.pjd2007-04-053-3/+3
|
* Implement SEEK_DATA and SEEK_HOLE extensions to lseek(2) as found inpjd2007-04-052-1/+65
| | | | | | OpenSolaris. For more information please refer to: http://blogs.sun.com/bonwick/entry/seek_hole_and_seek_data
* Add security.jail.mount_allowed sysctl, which allows to mount andpjd2007-04-051-0/+7
| | | | | | | | | | | | | | | | | | unmount jail-friendly file systems from within a jail. Precisely it grants PRIV_VFS_MOUNT, PRIV_VFS_UNMOUNT and PRIV_VFS_MOUNT_NONUSER privileges for a jailed super-user. It is turned off by default. A jail-friendly file system is a file system which driver registers itself with VFCF_JAIL flag via VFS_SET(9) API. The lsvfs(1) command can be used to see which file systems are jail-friendly ones. There currently no jail-friendly file systems, ZFS will be the first one. In the future we may consider marking file systems like nullfs as jail-friendly. Reviewed by: rwatson
* Avoid using intermediate variables by just comparing betweendelphij2007-04-051-27/+15
| | | | | | | | | | | | two values, the latter does not tend to have sign extension and/or overflow bugs, and makes the code more obvious. While I'm there, make use of a macro which is derived from bin/ps/ps.c: ps_compat() to improve the readability of the code. Suggested by: bde MFC after: 1 week
* Import amd64 assembly implementations of div(3) family from NetBSD.jkim2007-04-044-0/+51
| | | | Obtained from: NetBSD
* Add entry for dl_iterate_phdr.kan2007-04-031-0/+1
|
* Add stub for dl_iterate_phdr.kan2007-04-031-0/+10
|
* Use size_t instead of unsigned for pagesize-related values, in order tojasone2007-03-291-4/+8
| | | | | | | | | avoid downcasting issues. In particular, this change fixes posix_memalign(3) for alignments greater than 2^31 on LP64 systems. Make sure that NDEBUG is always set to be compatible with MALLOC_DEBUG. [1] Reported by: [1] Lee Hyo geol <hyogeollee@gmail.com>
* Remove the run promotion/demotion machinery. Replace it with red-blackjasone2007-03-281-430/+219
| | | | | | | | | | | | | | | | | | | | | | | trees that track all non-full runs for each bin. Use the red-black trees to be able to guarantee that each new allocation is placed in the lowest address available in any non-full run. This change completes the transition to allocating from low addresses in order to reduce the retention of sparsely used chunks. If the run in current use by a bin becomes empty, deallocate the run rather than retaining it for later use. The previous behavior had the tendency to spread empty runs across multiple chunks, thus preventing the release of chunks that were completely unused. Generalize base_chunk_alloc() (and rename it to base_pages_alloc()) to handle allocation sizes larger than the chunk size, so that it is possible to support chunk sizes that are smaller than an arena object. Reduce the minimum chunk size from 64kB to 8kB. Optimize tracking of addresses for deleted chunks. Fix a statistics bug for huge allocations.
* Change macro in order to refer to FreeBSD 7.0 instead of 7.0BSD.jasone2007-03-281-2/+2
| | | | Reported by: Michal Mertl <mime@traveller.cz>
* Update the IMPLEMENTATION NOTES section to reflect recent mallocjasone2007-03-281-13/+30
| | | | enhancements.
* Remove some stray roff formatting that caused incorrect rendering.jasone2007-03-281-1/+0
|
* Add a HISTORY section.jasone2007-03-281-0/+5
|
* Fix some subtle bugs for posix_memalign() having to do with integerjasone2007-03-241-18/+43
| | | | | | | | rounding and overflow. Carefully document what the various overflow tests actually detect. The bugs mostly canceled out, such that the worst possible failure cases resulted in non-fatal over-allocations.
* Fix posix_memalign() for large objects. Now that runs are extents ratherjasone2007-03-231-151/+297
| | | | | | | | than binary buddies, the alignment guarantees are weaker, which requires a more complex aligned allocation algorithm, similar to that used for alignment greater than the chunk size. Reported by: matteo
OpenPOWER on IntegriCloud