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>
diff --git a/include/openssl/base.h b/include/openssl/base.h index 71f283d..14c243b 100644 --- a/include/openssl/base.h +++ b/include/openssl/base.h
@@ -189,6 +189,10 @@ #define OPENSSL_MSVC_PRAGMA(arg) #endif +#if defined(BORINGSSL_UNSAFE_FUZZER_MODE) && \ + !defined(BORINGSSL_UNSAFE_DETERMINISTIC_MODE) +#define BORINGSSL_UNSAFE_DETERMINISTIC_MODE +#endif /* CRYPTO_THREADID is a dummy value. */ typedef int CRYPTO_THREADID;