openbsd/src/lib/libc/string, branch OPENBSD_6_6 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_6_6 2019-08-30T18:35:03+00:00 adapt to bitstring(3) renaming, and look at that bit_ffs(3) is the actual 2019-08-30T18:35:03+00:00 deraadt 2019-08-30T18:35:03+00:00 urn:sha1:724a6915f055167d35901dd9505fbbbdeabe1dae name we want to Xr... ok jmc More consistently put remarks about the less useful LC_* categoties, 2019-05-16T13:35:16+00:00 schwarze 2019-05-16T13:35:16+00:00 urn:sha1:f619d192fa7597c09bd37706d01926d28932de57 i.e. those other than LC_CTYPE, into the CAVEATS section, and standardize wording somewhat. OK jmc@ I am retiring my old email address; replace it with my OpenBSD one. 2019-01-25T00:19:26+00:00 millert 2019-01-25T00:19:26+00:00 urn:sha1:9395eef49000d5819f0d53eae86baa6e426dab86 Improve the description of locale dependency: 2019-01-18T07:43:36+00:00 schwarze 2019-01-18T07:43:36+00:00 urn:sha1:f9d7fe103d63d17a4a8c1e22d32afa8968b0377f * mention LC_COLLATE; * clarify that all these functions are infested, including the *_l() versions; * avoid ENVIRONMENT, these functions don't inspect it; * and point to the C library functions that change the locale. OK millert@ As per POSIX, when str{,r}chr is comparing it should convert c to a char. 2018-10-01T06:37:37+00:00 martijn 2018-10-01T06:37:37+00:00 urn:sha1:14762f7fed750ccdd7b8473696771f67b80a6639 The C implementation of str{,r}chr are not linked to the build, because assembly implementations are used, but change to code for easier reference. At least the i386 and amd64 are checked and seem to do the correct thing. Found thanks to the csh any/strchr change. minor pointers and OK millert@ Add a missing header when compiling with -DDEBUG 2018-04-30T07:44:56+00:00 denis 2018-04-30T07:44:56+00:00 urn:sha1:a8b69163d3bb4f0d18483bcbdec0f92c676330df With advice from jca@ OK jca@ millert@ Instead of trying to handle ffs() with the normal rename-mark-hidden-and-alias 2018-01-18T08:23:44+00:00 guenther 2018-01-18T08:23:44+00:00 urn:sha1:35352e830aefedf0f54a965ee2aaf8a6ff643231 dance, mark it protected. This works better for both gcc and clang: gcc blocks overriding of internal calls, while clang permits inlining again. ok otto@ clang doesn't propagate attributes like "asm labels" and "visibility(hidden)" 2017-11-29T05:13:57+00:00 guenther 2017-11-29T05:13:57+00:00 urn:sha1:91809a23ddd15af26964fe79c11bc52b08afeb95 to builtins like mem{set,cpy,move} and __stack_smash_handler. So, when building with clang, instead mark those as protected visibility to get rid of the PLT relocations. We can't take the address of them then, but that's ok: it's a build-time error not a run-time error. ok kettenis@ GNU ld has prefixed the contents of .gnu.warning.SYMBOL sections 2017-11-28T06:55:49+00:00 tb 2017-11-28T06:55:49+00:00 urn:sha1:8498b91851192781ec9ed2dd8420226001473ef7 with "warning: " since 2003, so the messages themselves need not contain the prefix anymore. From Scott Cheloha ok jca, deraadt Add STANDARDS: denis@ spotted that it was missing. 2017-10-12T15:22:32+00:00 schwarze 2017-10-12T15:22:32+00:00 urn:sha1:aee5e9fddc0c77e82e75ef5c6fd6443bd2d842e3 OK deraadt@ jca@ jmc@