| commit | 90c001ac9e1d92a1a95d191d1640ab5337a937e5 | [log] [tgz] |
|---|---|---|
| author | Alexey Samsonov <vonosmas@gmail.com> | Wed Apr 09 15:36:48 2025 -0700 |
| committer | GitHub <noreply@github.com> | Wed Apr 09 15:36:48 2025 -0700 |
| tree | 1223e7e161654ee0e616b350f7fdfa5f7dcd7ed5 | |
| parent | 58b91d10a4c9dcd71ea0bcf6ff702a46dad147cb [diff] |
[libc][bazel] Use Bazel aspects to implement libc_release_library. (#134948) Instead of creating hundreds of implicit "filegroup" targets to keep track of sources and textual headers required to build each libc function or helper library, use Bazel aspects (see https://bazel.build/versions/8.0.0/extending/aspects), which enable transparent collection of transitive sources / textual headers while walking the dependency DAG, and minimizes the Starlark overhead. Co-authored-by: Jordan Rupprecht <rupprecht@google.com>
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.