[clang][ssaf] Add SARIF transformation-report format (#208327) Adds the built-in `TransformationReportFormat`, registered under the file extension `sarif`. The writer drives clang's existing `SarifDocumentWriter` (`clang/Basic/Sarif.h`) to produce a SARIF 2.1.0 JSON document. The tool driver name is `clang-ssaf`; the long `fullName` carries the transformation's name. Token-range `CharSourceRange`s are canonicalized to char ranges via `clang::Lexer::getAsCharRange` before being attached to results; invalid ranges (including default-constructed ones) are treated as "no location" — the writer omits the result's `locations` key rather than fabricating one. Source edits are not embedded in the report; the writer never emits a `fix` or `fixes` key. Anchored via `SSAFSARIFTransformationReportFormatAnchorSource` so static builds keep the registration. Assisted-By: Claude Opus 4.7
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.