[llvm] [DevPolicy] Add guidelines for fuzzer-generated issue reports (PR #112372)

Shafik Yaghmour via llvm-commits llvm-commits at lists.llvm.org
Tue Oct 15 10:08:26 PDT 2024


================
@@ -853,6 +853,57 @@ their patch with every possible configuration.
 * 3rd step: If Galina could not help you, please escalate to the
   `Infrastructure Working Group <mailto:iwg at llvm.org>`_.
 
+Guidelines for fuzzer-generated issues
+--------------------------------------
+
+Fuzzing is a valuable tool for finding compiler bugs, and the LLVM project
+welcomes fuzzer-generated test cases. However, some additional guidelines
+should be followed to make such reports maximally useful.
+
+Fuzzer-generated issues should indicate that they are such, either in the
+issue description, or (for organization members) by applying the
+``fuzzer-generated`` label. This helps us prioritize issues. The remaining
----------------
shafik wrote:

Note currently folks are using `clang:fronted:fuzzer` and `compiler-rt:fuzzer` I don't have a strong preference here but I would be curious to know how folks feel about having one bucket Vs more fine grained ones. 

https://github.com/llvm/llvm-project/pull/112372


More information about the llvm-commits mailing list