This duplicates some of the BUILD dependency tree to go around the need to link huge bottleneck dependencies (such as `//tensorflow/core:framework`). Until TF can use `cc_shared_library` in a stable way (and all support in Bazel exists), we will need to use the duplicated tree for fuzzing.
PiperOrigin-RevId: 317326319
Change-Id: I1493e3ae7340298971fe15bd3702b63657f9bf9f
Since we have a fuzzer for `Status`, we no longer need `demo_fuzz.cc` and the associated `demo_fuzz` `BUILD` target.
The `Status` fuzzer fails to compile in OSSFuzz as `string` is not `std::string`. Fix this in the same commit.
PiperOrigin-RevId: 316184164
Change-Id: I7001533e899c0aea399da19fd1b72099294d6be2
This should allow us to test fuzzing infrastructure with minimal dependencies.
Since `Status` is used almost everywhere, we need to ensure that the common functionality is safe. We don't expect many crashes from this fuzzer since we only create a status and then look at the error message from it but this is a good test of the fuzzing infrastructure, with minimal dependencies (thus, it is a good test to weed out linker bloat and other linker issues).
PiperOrigin-RevId: 316163409
Change-Id: I62d192348b5f90209ce9188039e4962fe34872a8
This should enable us to create fuzzers that can be used in open source, both in OSSFuzz (in the end, this is part of stabilizing the OSSFuzz integration) and by themselves alone (by passing the corresponding flags).
PiperOrigin-RevId: 315182751
Change-Id: I3b6c38b0bd0613fcfe12d0d61726a5a4bab9c09c
