kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix comment on OPENSSL_memcmp, etc.

Browse Source 
I thought I'd rewritten this, but apparently didn't. The old version
dated to a prior iteration which used macros.

Change-Id: Idefbdb2c11700a44dd5b0733b98efec102b10dd2
Reviewed-on: https://boringssl-review.googlesource.com/12968
Reviewed-by: Adam Langley <agl@google.com>
This commit is contained in:
David Benjamin 2016-12-21 16:00:13 -05:00 committed by Adam Langley
parent 17cf2cb1d2
commit ec6b530683
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
crypto/internal.h
View File

@ -530,9 +530,8 @@ OPENSSL_EXPORT void CRYPTO_free_ex_data(CRYPTO_EX_DATA_CLASS *ex_data_class,
* miscompile code due to this rule. See also
* https://www.imperialviolet.org/2016/06/26/nonnull.html
*
* If building BoringSSL itself, replace C standard library functions with more
* well-behaved versions. Due to some C++ toolchains defining versions of these
* functions under namespaces, this is limited to our C files.
* These wrapper functions behave the same as the corresponding C standard
* functions, but behave as expected when passed NULL if the length is zero.
*
* Note |OPENSSL_memcmp| is a different function from |CRYPTO_memcmp|. */