Have fuzz/c programs define WUFFS_CONFIG__MODULES

Before:
$ time ./build-fuzz.sh fuzz/c/std/json_fuzzer.c
real	0m0.822s
user	0m0.792s
sys	0m0.031s

After:
$ time ./build-fuzz.sh fuzz/c/std/json_fuzzer.c
real	0m0.294s
user	0m0.271s
sys	0m0.024s
This commit is contained in:
Nigel Tao committed 2020-03-01 13:11:36 +11:00
1 parent 16867779be
commit 260995cb05
3 files changed
+37 -1

No files matched your search

+11
View File
@@ -42,6 +42,17 @@ It should print "PASS", amongst other information, and exit(0).
// compiling it.
#define WUFFS_IMPLEMENTATION
// Defining the WUFFS_CONFIG__MODULE* macros are optional, but it lets users of
// release/c/etc.c whitelist which parts of Wuffs to build. That file contains
// the entire Wuffs standard library, implementing a variety of codecs and file
// formats. Without this macro definition, an optimizing compiler or linker may
// very well discard Wuffs code for unused codecs, but listing the Wuffs
// modules we use makes that process explicit. Preprocessing means that such
// code simply isn't compiled.
#define WUFFS_CONFIG__MODULES
#define WUFFS_CONFIG__MODULE__BASE
#define WUFFS_CONFIG__MODULE__JSON
// If building this program in an environment that doesn't easily accommodate
// relative includes, you can use the script/inline-c-relative-includes.go
// program to generate a stand-alone C file.