A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=libressl-v2.1.2 2014-12-09T07:28:46+00:00 2014-12-09T07:28:46+00:00 deraadt 2014-12-09T07:28:46+00:00 urn:sha1:5cd5e0377a60528d90a8552d4705f760c6e324ee the same thingies. Therefore these "lists of functions" man pages can go away. Hurray! I've wanted these pages to die for around 10 years! ok ingo (and i think jmc) 2014-11-30T21:21:59+00:00 schwarze 2014-11-30T21:21:59+00:00 urn:sha1:2f8f81cd7d51edc2c22f90355222b5dafedab140 The former is not used anywhere in NetBSD, FreeBSD, or DragonFly and not supported by groff, so i'm going to delete it from mandoc(1). We don't need two macros for the same thing. 2014-11-30T19:43:57+00:00 deraadt 2014-11-30T19:43:57+00:00 urn:sha1:d8f66904ee035f3e8b0d2d91fedb956995e16678 (potentially) MD versions (function dependent, not filename dependent) split out memcpy/memmove/bcopy and strchr/index/strrchr/rindex Bring back amd64 .S versions And the final touch: switch all architectures temporarily to MI memcpy.c, which contains syslog + abort for overlapping copies. A nice harsh undefined behaviour. We will clean the entire userland of the remaining issues in this catagory, then switch to the optimised memcpy which skips the memmove check. I tried to cut this change into pieces, but testing each sub-step on every architecture is too time consuming and mindnumbing. ok miod 2014-10-11T14:40:42+00:00 schwarze 2014-10-11T14:40:42+00:00 urn:sha1:ab43d18a8093fc40aa2aab3379dd2bffb41fcae4 i looked a bit closer and found instances before Reno, so correct HISTORY. References: http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.1cBSD/usr/src/ucb/dbx/defs.h http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD/usr/src/etc/inetd.c http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Reno/src/lib/libc/string/strdup.c ok deraadt@ 2014-10-08T05:27:17+00:00 deraadt 2014-10-08T05:27:17+00:00 urn:sha1:0f2228d5a81407b4ea5f868098096e296898877b 2014-07-09T17:08:21+00:00 naddy 2014-07-09T17:08:21+00:00 urn:sha1:ff0f26044242f360fa59cf8865351a7a458cdbd4 new wording agreed by at least kettenis@ millert@ otto@ 2014-06-21T20:22:15+00:00 tedu 2014-06-21T20:22:15+00:00 urn:sha1:71b30cdd53305a1e04e5f93862d35e680d38af91 artificially constrain alternative implementations. ok deraadt 2014-06-21T02:34:26+00:00 matthew 2014-06-21T02:34:26+00:00 urn:sha1:9c52c243dba540e16f6f2a3f88131dd7f668f419 Modern compiler toolchains are capable of optimizing even across translation unit boundaries, so simply moving the memory clearing into a separate function is not guaranteed to clear memory. To avoid this, we take advantage of ELF weak symbol semantics, and insert a call to an empty, weakly named function. The semantics of calling this function aren't determinable until load time, so the compiler and linker need to keep the memset() call. There are still ways a toolchain might defeat this trick (e.g., optimistically expecting the weak symbol to not be overloaded, and only calling memset() if it is; promoting weak symbols to strong symbols at link-time when emitting a static binary because they won't be interposed; implementing load-time optimizations). But at least for the foreseeable future, these seem unlikely. ok deraadt 2014-06-13T02:12:17+00:00 matthew 2014-06-13T02:12:17+00:00 urn:sha1:62fc04d99bb7daa7bc91641190502c1d2b3251cc ok deraadt, jmc, tedu 2014-06-10T04:17:37+00:00 deraadt 2014-06-10T04:17:37+00:00 urn:sha1:a13b202796a212c4c4e553e85d8bad24bbdffe07