now that there is essentially no malloc.conf;
text tweaked by deraadt; ok otto deraadt

libs have it, it is a function that is considered harmful, so:
Delete malloc_usable_size(). It is a function that blurs the line
between malloc managed memory and application managed memory and
exposes some of the internal workings of malloc.  If an application
relies on that, it is likely to break using another implementation
of malloc.  If you want usable size x, just allocate x bytes. ok
deraadt@ and other devs

here could creates non-uniformity since very short fetches of 0 would
be excluded.  blocks of 0 are just as random as any other data, including
blocks of 4 4 4..  This is a misguided attempt to identify errors from the
entropy churn/gather code doesn't make sense, errors don't happen.
ok bcook

PROTO_NORMAL().  Problem noted by deraadt@

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@

ok nicm

This variable is only used in the parent context so there is no issue.
ok kettenis

With advice from jca@
OK jca@ millert@

Based on discussion here https://github.com/libressl-portable/openbsd/pull/82
Suggested fix from jsing@

don't need to use sys/param.h at all, guess which one i believe is
greater namespace polution
ok otto

ok guenther kettenis

- Start with a full page of struct region_info's
- Save an mprotect in the init code: allocate 3 pages with none and
make the middle page r/w instead of a r/w allocation and two calls to make the
guard pages none

junked
- freezero(): only clear requested size

came also up with this diff. Simple, no bias and benchmarks show the extra
random calls disappear in te measurement noise.

but at that time ffs function calls were generated instead of the
compiler inlining the code.  Now that ffs is marked protected in
libc this is handled better.  Thanks to kshe who prompted me to
look at this again.

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@

some cleanup; tested by sthen@ on a ports build

relevant. from Mark Karpilovskij.
ok millert

cleanups.  From Jan Kokemueller.  OK deraadt@

(w/ _dlctl reference) into static executables.  It's all Mark's code so
put his preferred copyright on it.
ok kettenis@

to control which symbols are exported from the shared library.
ok guenther@, deraadt@, jca@

_libc___cxa_thread_atexit_impl reference on gcc architectures that breaks
the build.

interface is also made available as __cxa_thread_atexit_impl to satisfy the
needs of GNU libstdc++.
ok guenther@, millert@

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@

with "warning: " since 2003, so the messages themselves need not
contain the prefix anymore.
From Scott Cheloha
ok jca, deraadt

but not all.  From Peter J. Philipp.

which results in an internal double free when internal functions are not
in use.
ok otto@

OK deraadt@ jca@ jmc@

ok tb@ tedu@