diff options
author | schwarze <> | 2018-04-01 00:36:28 +0000 |
---|---|---|
committer | schwarze <> | 2018-04-01 00:36:28 +0000 |
commit | d00bb6331cc6c256da5ab5bbf5b24f1751ad367d (patch) | |
tree | d68bda8b9354fb1fa31660be4c25fedb4487eef3 /src/lib/libc/stdlib | |
parent | fd23e46da856d00343d92965373b3cdb9875d6af (diff) | |
download | openbsd-d00bb6331cc6c256da5ab5bbf5b24f1751ad367d.tar.gz openbsd-d00bb6331cc6c256da5ab5bbf5b24f1751ad367d.tar.bz2 openbsd-d00bb6331cc6c256da5ab5bbf5b24f1751ad367d.zip |
When you replace an element in a sorted array with something
arbitrarily different, the array is in general no longer sorted.
This commit copies a small hidden bugfix from the OpenSSL commit
https://github.com/openssl/openssl/commit/fbb7b33b
the rest of which is merely cosmetics.
I discovered the bug independently while documenting sk_find(3).
Keep the library's idea of when an empty stack or a one-element stack
is sorted and when it is not bug-compatible with OpenSSL, even though
in fact, empty and one-element stacks are of course always sorted.
OK beck@
Diffstat (limited to 'src/lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions