commit | 42622c79592b98b899d787c89db11cea1b540b96 | [log] [tgz] |
---|---|---|
author | Keith Smiley <keithbsmiley@gmail.com> | Thu Apr 24 16:22:56 2025 -0700 |
committer | GitHub <noreply@github.com> | Thu Apr 24 16:22:56 2025 -0700 |
tree | 24c9200580e3a816406256fc88ce27708d183799 | |
parent | 5b16941f5707c3a326b688e0954f8882d8a36951 [diff] |
[bazel] Depend on full Utility library in lldb (#137265) Since 6493345c5ab96f60ab5ee38272fb6635f2083318 the utility library is needed by the driver. Since liblldb's exports are limited with -exports_symbols_list on macOS, some symbols like `__ZN12SelectHelper10FDSetWriteEi` are not exported from liblldb and therefore cause linker failures on macOS only. In the cmake the driver now depends on the full utility library, even though that leads to some duplication of symbols, so it should be safe for us to do in bazel as well.
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.