boringssl/crypto/poly1305
David Benjamin 17cf2cb1d2 Work around language and compiler bug in memcpy, etc.
Most C standard library functions are undefined if passed NULL, even
when the corresponding length is zero. This gives them (and, in turn,
all functions which call them) surprising behavior on empty arrays.
Some compilers will miscompile code due to this rule. See also
https://www.imperialviolet.org/2016/06/26/nonnull.html

Add OPENSSL_memcpy, etc., wrappers which avoid this problem.

BUG=23

Change-Id: I95f42b23e92945af0e681264fffaf578e7f8465e
Reviewed-on: https://boringssl-review.googlesource.com/12928
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
2016-12-21 20:34:47 +00:00
..
asm Switch perlasm calling convention. 2016-06-27 21:59:26 +00:00
CMakeLists.txt Revert "Enable upstream's Poly1305 code." 2016-03-29 22:47:11 +00:00
internal.h Revert "Enable upstream's Poly1305 code." 2016-03-29 22:47:11 +00:00
poly1305_arm_asm.S Revert "Enable upstream's Poly1305 code." 2016-03-29 22:47:11 +00:00
poly1305_arm.c Work around language and compiler bug in memcpy, etc. 2016-12-21 20:34:47 +00:00
poly1305_test.cc Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
poly1305_tests.txt Be consistent about 𝑥_tests.txt 2016-06-06 15:57:46 +00:00
poly1305_vec.c Use UINT64_C instead of unsigned long long integer constant. 2016-04-11 16:08:14 +00:00
poly1305.c Work around language and compiler bug in memcpy, etc. 2016-12-21 20:34:47 +00:00