[libc++] Simplify and optimize the run-benchmarks script (#181382) Instead of configuring and running the benchmark suite once for SPEC and once for the microbenchmarks, run it only once for everything. This saves a configuration of the test suite (which includes building Google Benchmark). To replicate the functionality we had with --disable-microbenchmarks (whose goal was mostly to run only SPEC), introduce a --filter argument that can be used to select exactly which benchmarks are run. This is simpler and more powerful. Making this work requires hardcoding the only C++ standard that works for SPEC (C++17) inside spec.gen.py instead of expecting it to be set correctly when running the test suite.
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.