* Put AES ctx on the heap
This forces people to use the ``ctx_release`` functions, because otherwise there will be leaks
* Put fips202 on the heap
* Add much more docs for fips202.h
* fixup! Put fips202 on the heap
* Put SHA2 on the heap-supporting API
* Fix clang-tidy warnings
* Fix unreachable free() in falcon
* Fix McEliece8192128f-sse GNU Makefile
* Add McEliece reference implementations
* Add Vec implementations of McEliece
* Add sse implementations
* Add AVX2 implementations
* Get rid of stuff not supported by Mac ABI
* restrict to two cores
* Ditch .data files
* Remove .hidden from all .S files
* speed up duplicate consistency tests by batching
* make cpuinfo more robust
* Hope to stabilize macos cpuinfo without ccache
* Revert "Hope to stabilize macos cpuinfo without ccache"
This reverts commit 6129c3cabe1abbc8b956bc87e902a698e32bf322.
* Just hardcode what's available at travis
* Fixed-size types in api.h
* namespace all header files in mceliece
* Ditch operations.h
* Get rid of static inline functions
* fixup! Ditch operations.h
* Add state destroy to SHA2 API
* Include optimized SPHINCS+ implementations
I've generated new implementations from the sphincsplus repository.
* Don't destroy sha256ctx after finalize
* Attempt to shut up MSVC
* Make sure to drop errors in rmtree
* Integrate Kyber-AVX2 into PQClean
* Fix types and formatting in Kyber
* Workaround a valgrind crash
* Remove comment in shuffle.s
* Remove some extraneous truncations
* fixup! Fix types and formatting in Kyber
* Add support for specifying architecture and feature limits
* cpuinfo not supported on ppc
* Detect 32-bit python interpreter on 64-bit CPU
* Fix bugs in isolated tests
* Also support restricting operating system
* Enable valgrind exit errorcode
It seems we were not doing anything with the valgrind results... D:
* Use --exit-on-first-error if available
* Revert "Merge pull request #182 from PQClean/rainbow"
This reverts commit 8a008417fe, reversing
changes made to d4b612fe9a.
* Do tests with pytest to run them in parallel
* attempt to handle merge commits better for PR test path
Similar to how we solved this for travis
* Clean up imports
* don't run valgrind if not specified slow_test
* Fix functest after initializer rename
* upload tests results as junit
* Upload test-common files since #200 got merged
* Catch test results upload failure
* Move test support files into tests directory
* Fix common tests dir in test
* Fix Windows Makefile for common tests
* notrandombytes.obj should be in TEST_COMMON_DIR
There are schemes, like SABER (#192) that have more than one principal
submitter. Consistency warrants that we turn it into a list for all
schemes and don't do something with allowing either a str or a list:
that would just be very annoying to parse.
Closes#194
