BORINGSSL_UNSAFE_FUZZER_MODE implies BORINGSSL_UNSAFE_DETERMINISTIC_MODE.
We have at least three different external build definitions for the fuzzers. That's enough that requiring each of them account for the split fuzzer mode is probably too much turbulence. Change-Id: I96dbb12a2b4f70bfa1b04cd0d15fda918bbf51d6 Reviewed-on: https://boringssl-review.googlesource.com/12183 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com>
This commit is contained in:
parent
c5ac2b6c78
commit
14c7e8d282
@ -189,6 +189,10 @@ extern "C" {
|
|||||||
#define OPENSSL_MSVC_PRAGMA(arg)
|
#define OPENSSL_MSVC_PRAGMA(arg)
|
||||||
#endif
|
#endif
|
||||||
|
|
||||||
|
#if defined(BORINGSSL_UNSAFE_FUZZER_MODE) && \
|
||||||
|
!defined(BORINGSSL_UNSAFE_DETERMINISTIC_MODE)
|
||||||
|
#define BORINGSSL_UNSAFE_DETERMINISTIC_MODE
|
||||||
|
#endif
|
||||||
|
|
||||||
/* CRYPTO_THREADID is a dummy value. */
|
/* CRYPTO_THREADID is a dummy value. */
|
||||||
typedef int CRYPTO_THREADID;
|
typedef int CRYPTO_THREADID;
|
||||||
|
Loading…
Reference in New Issue
Block a user