| commit | 9d88ffe7f7b4a46d3bcb7bbdf0d7eb037ab5ba04 | [log] [tgz] |
|---|---|---|
| author | Lang Hames <lhames@gmail.com> | Thu Feb 06 16:04:35 2025 +1100 |
| committer | Lang Hames <lhames@gmail.com> | Thu Feb 06 16:10:30 2025 +1100 |
| tree | 9f0dfdd12e12b4df28de1ed0bb1a261317368793 | |
| parent | c9446ff8a3d9535854404aef771da362856a5f02 [diff] |
[JITLink] Handle compact-unwind records that depend on DWARF FDEs. Compact-unwind encodings are more limited than DWARF frame descriptions. For functions whose frame layout cannot be described by a compact unwind encoding, the encoding for the function will specify "use DWARF", and the corresponding unwind-info record will use the low bits of the encoding to point to the FDE for the function. We test this with a frame-pointer=none function, since these frame layouts always triger a fall-back to DWARF on arm64.
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.