wireguard-openbsd/lib/libc/citrus, branch master

Trivial cleanup: Pass pointers of the correct types to the private

2016-09-07T17:15:06Z

functions and delete a macro that is used in only one place; no functional change. This completes the audit of the citrus directory (only 3 files left).

trivial cleanup: delete inline attribute on static function,

2016-09-07T17:10:43Z

leave that decision to the compiler; no functional change

trivial cleanup:

2016-09-07T17:06:23Z

- delete unused headers - add missing function prototype - delete needless casts of return values - KNF: return is not a function - KNF: do not use a pointer as a boolean - consistent wording in comments: s/octets/bytes/ OK gcc: no object change after strip -g

Delete some abstraction that we don't and won't need.

2016-09-05T09:47:02Z

Declare functions rather than generating declarations with macros. Just call functions rather than mainting function pointer tables. Purge unused arguments. Simplify mbstate_t casting. Garbage collect one empty and one unused function. As a bonus, make mbsinit(3) work at all, it returned garbage in the past due to a missing cast when passing mbstate_t. Apart from that, no functional change. No libc bump needed; only private functions are removed and change prototype and only private structs change size. OK stsp@ mpi@; deraadt@ likes the general direction.

delete old lint ARGSUSED comments

2015-11-01T03:45:28Z

Tighten the ranges in wcrtomb(3).

2015-10-13T02:17:46Z

By definition, the range of valid Unicode code points is the union of U+0000..U+D7FF and U+E000..U+10FFFF (see Unicode 8.0.0, chapter 3.9). In UTF-16, the encoded values that would represent U+D800..U+DFFF are used for surrogate pairs. UTF-8 has no concept of surrogate pairs; attempting to treat them as regular code points violates the standard and makes no sense besides. ok stsp@

Make wcrtomb() more readable by weeding out range errors up front,

2015-10-12T17:50:51Z

doing ASCII handling once rather than twice, and using <= rather than ((&~)==) obfuscation (which already caused a bug in the past). No functional change. Joint work with and OK stsp@ semarie@ bentley@

Code points U+10000 to U+fffff are valid, too.

2015-10-10T13:54:22Z

Fixing a regression in wcrtomb(3) found with the mandoc testsuite that was caused by the last commit. OK semarie@ bentley@

correct a range problem in citrus-utf8 version of wcrtomb(3), in order to match

2015-09-26T14:22:40Z

RFC 3629 (limiting the range of UTF-8 to 0x10FFFF). it is the counterpart of a previous commit correcting mbrtowc(3). problem spotted by stsp ok bentley@ stsp@

off-by-one for the previous patch. the limit is inclusive: 0x10ffff is a valid codepoint.

2015-09-05T15:22:04Z

ok stsp@