anonymouspc wrote: TODO:
1. Support nested compile outputs in SARIF mode - Attach `SARIFResults.relatedLocations (diagnostics, with level = note)` to `SARIFResult.relatedLocations (with level = error/warning)`. - *As both GCC and MSVC supports nesting in SARIF mode. Below is an example of GCC output as rendered by [my vscode sarif extension](https://github.com/anonymouspc/cppsarif):* - <img width="1280" height="832" alt="nested-gcc-sarif-output" src="https://github.com/user-attachments/assets/a00008a2-eec0-453f-92b0-1953e1e3f75f"; /> 2. Add `sarif.run.result.relatedLocation.relationship` - Introduce `relationship` (with value = either `"include"` or `"isIncludedBy"`), to represent inclusion relationships between artifacts. 3. Add compilation options for `clang++` to export `.sarif` files while still emitting normal text diagnostics - Many of us wanna see text in stderr and at the same time save `.sarif` files for other use. - Currently, `clangd` immediately crashes when `clang++` is invoked with `-fdiagnostics-format=sarif`, because `clangd` simply forwards `-fdiagnostics-format` argument but expects text-form diagnostics. - GCC solves this via `-fdiagnostics-add-output=sarif:file=path/to/file.sarif`. *(If clang is willing to accept contributions on SARIF diagnostic, I will be thrilled to complete the above targets (however, must be after my final exam in school at about 12/21...))* # Thank you! https://github.com/llvm/llvm-project/pull/170415 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
