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

[Yingwei Zheng via llvm-commits]

================
@@ -853,6 +853,69 @@ 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.
+
+Issues should include a minimized reproducer (including both the necessary code
+and command line arguments) both as part of the issue description and as a
+godbolt.org link. An effort should be made to deduplicate issues that likely
----------------
dtcxzyw wrote:

```suggestion
godbolt.org/alive2.llvm.org link. An effort should be made to deduplicate issues that likely
```
alive2.llvm.org is useful for reporting miscompilation bugs without constructing an executable program.



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