Investigate why the number of PCs varies so wildly in libFuzzer builds on Windows |
|||
Issue descriptionFor example, on Linux: base64_decode_fuzzer and base64_encode_fuzzer have about 20k PCs. On Windows: decode has 68 and encode has 44k. When I remove the calls to CHECK and CHECK_EQ from encode, it ends up with about 70 PCs. I'm guessing linking is not stripping as much dead code as it should (on Linux as well, but that is a separate and known issue with ASAN).
,
Sep 17
,
Sep 17
Using /O1 instead of /O2 (as done on Linux, thanks to optimize_for_fuzzing) looks promising, in bringing the encode fuzzer to ~29k edges, as opposed to ~25k on Linux. It also reduced the size of all files produces (ie: lib, pdb, and exe)
,
Nov 20
This no longer looks like a problem. The fuzzers in the example have the following pc counts on the latest build: base64_decode_fuzzer: 46 base64_encode_fuzzer: 1710 |
|||
►
Sign in to add a comment |
|||
Comment 1 by metzman@chromium.org
, Sep 17