| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
As best I can tell it wasn't actually possible for the value to be
used uninitialized, since it was initialized if m_outer_summands > 1
and only used if m_outer_summands was at least 2.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Remove -Wsuggest-attribute=noreturn from maintainer mode flags as it
seems like outside of the assertion failure macro any other suggestion
would always be a false positive (an unimplemented function or the like).
Or at least, if such a function needing noreturn to assist with static
analysis is added in the future it will be obvious, by virtue of the
static analyzer warnings which occur due to the missing noreturn
preventing the analyzer from understanding code flow.
|
|\ |
|
| | |
|
| |
| |
| |
| | |
GH #369
|
| |
| |
| |
| | |
Remove bogus virtual destructor on Entropy_Accumulator (has no virtuals)
|
| | |
|
|/
|
|
| |
Works around a libstdc++ bug when fuzzing with libFuzzer
|
|\
| |
| |
| |
| |
| | |
By adopting MemoryStatusEx, this drops support for XP and Server 2003
which do not implement this API. This is considered a feature as these
versions are already EOLed by Microsoft.
|
| |
| |
| |
| |
| | |
* GetTickCount is replaced by GetTickCount64(): see https://msdn.microsoft.com/en-us/library/windows/desktop/ms724408(v=vs.85).aspx for details
* GlobalMemoryStatus is replaced by GlobalMemoryStatusEx: see https://msdn.microsoft.com/en-us/library/windows/desktop/aa366589(v=vs.85).aspx for details
|
|\ \ |
|
| | | |
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
In some cases this can offer better optimization, via devirtualization.
And it lets the user know the class is not intended for derivation.
Some discussion in GH #402
|
|\ \ \ |
|
| |/ / |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
# Conflicts:
# src/build-data/cc/gcc.txt
|
| | | |
|
| | |
| | |
| | |
| | | |
to not break compatibility with older gcc versions (available in gcc 5.1)
|
| | |
| | |
| | |
| | | |
found by gcc with -Wsuggest-override
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
In addition don't declare virtual functions noreturn
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This avoids a scan over the entire 0 - 0xFFFF space which is mostly
empty, by instead keeping a second list in tls_suite_info which is
exactly the keys for which the switch statement has values.
This scan is only ever done once (when first needed) but removing it
is sufficient to increase AFL's throuhput by 4x since it goes through
a full startup on each test.
|
| |
| |
| |
| | |
fix PVS-Studio perfomance warnings
|
| |
| |
| |
| | |
Missing . in compression extension, wrong name for buf-size option
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Expose provider param in PK_Key_Agreement API
Handle multiple providers in key agreement tests
Fix some funky formatting of P-521 EC points in ecdh.vec which was
being rejected by OpenSSL; for whatever reason the CAVS file had
the affine coords with far more leading zeros than necessary.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Has the same effect as using ctgrind, but without requiring a
custom-compiled valgrind binary.
Add ct checking annotations to the SSSE3 AES code.
|
| | |
|
| |
| |
| |
| | |
Interop tested with mbed TLS
|
| |
| |
| |
| | |
Only has vectors for NIST curves (data taken from NIST CAVS file)
|
| |
| |
| |
| |
| |
| | |
There was a special case for small scalars which managed to forget
that the integer 3 also fits into two bits. Found by adding a new set
of ECC point mul tests for the NIST curves.
|
| |
| |
| |
| |
| |
| | |
Aligning the calls makes it easier to read the index travel
Add a date to the generated output file
|
| |
| |
| |
| | |
j is never more than 30 in this loop
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug found by Daniel Neus
The function wasn't being used anywhere in the library (and was only
added in 1.11.20) so it seems easier to remove than fix. And removing
it serves to put any user on notice that something bad happened;
Daniel tested this as returning just 0 when bits >= 32 with his
system's compiler.
|
| |
| |
| |
| |
| | |
(Two part commit with 64caa9a to work around git's insane implied
rename system)
|