[clang-doc] Add basic benchmarks for library functionality (#182620) clang-doc's performance is good, but we suspect it could be better. To track this with more fidelity, we can add a set of GoogleBenchmarks that exercise portions of the library. To start we try to track high level items that we monitor via the TimeTrace functions, and give them their own micro benchmarks. This should give us more confidence that switching out data structures or updating algorthms will have a positive performance impact. Note that an LLM helped generate portions of the benchmarks and parameterize them. Most of the internal logic was written by me, but the LLM was used to handle boilerplate and adaptation to the harness.
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.