Reid Kleckner
821afb2ed8
Tracking issue: https://github.com/llvm/llvm-project/issues/201242 Migration guide docs: https://llvm.org/docs/SphinxQuickstartTemplate.html#markdown-migration-guidelines RFC: https://discourse.llvm.org/t/rfc-make-myst-markdown-the-llvm-docs-format-rip-rest/90840 This was prepared with rst2myst plus LLM-assisted cleanup. I paged through all the generated HTML looking for migration artifacts, and all of the differences I could find appear to be formatting error corrections. Please spot check my work and approve if it looks good.
830 B
(fuzzing)=
Fuzzing for LLVM-libc functions
Fuzz tests are used to ensure quality and security of LLVM-libc implementations.
All fuzz tests live under the directory named fuzzing. Within this
directory, the fuzz test for a libc function lives in the same nested directory
as its implementation in the toplevel src directory. The build target
libc-fuzzer builds all of the enabled fuzz tests (but does not run them).
Types of fuzz tests
As of this writing, there are two different kinds of fuzz tests. One kind are the traditional fuzz tests which test one function at a time and only that particular function. The other kind of tests are what we call as the differential fuzz tests. These tests compare the behavior of LLVM libc implementations with the behavior of the corresponding functions from the system libc.