* 'master' of github.com:jedisct1/libsodium:
Bench: don't tie the printed result to the number of iterations
Make the number of iterations configurable; reduce the default
Add an interesting test case for a custom randombytes_uniform implementation
Add a benchmark mode
randombytes test: restore the salsa20-based rng at the end, for benchmarks
Indent
* 'master' of github.com:jedisct1/libsodium:
Simplify
Just a simple script to match constants with functions
+ emscripten-wasm.sh
Update the exported list of JS symbols
Add *_messagebytes_max() wrappers
Revert "wasm tests: skip over *.asm.js files"
wasm tests: skip over *.asm.js files
[Findsodium.cmake] DON'T OVERWRITE LIBRARY SUFFIXES (#576)
Revert "+ sodium_alloc_overhead()"
+ sodium_alloc_overhead()
Remove TOTAL_MEMORY from wasm builds
Include private/common.h for COMPILER_ASSERT
Sort
Node need for --expose-wasm any more with recent nodejs versions
asmjs builds need to be done separately to get actual asmjs code
and not almost-asmjs code.
Don't build html pages. It doesn't change anything, and support for
asmjs in libsodium.js remains a tricky problem to solve.
Projects using the legacy API are unlikely to use these new macros.
OTOH, people using the Sodium API would be puzzled about the missing
16 bytes in the secretbox and box APIs.
More importantly, these macros are designed for bindings.
Having these bindings enforce proper limits (for the *_easy API
that they all use) and yet have the underlying library call
sodium_misuse() would be sad.
