| commit | 99a235499337aff27d087c31916d6785d2e9a263 | [log] [tgz] |
|---|---|---|
| author | Jacek Caban <jacek@codeweavers.com> | Wed Sep 11 14:46:40 2024 +0200 |
| committer | GitHub <noreply@github.com> | Wed Sep 11 14:46:40 2024 +0200 |
| tree | dbc4708df753046dff75c2e7e6247c3638f3dac6 | |
| parent | 49b57df16144450331b4f90332d6918168b2a306 [diff] |
[LLD][COFF] Add support for ARM64EC import call thunks. (#107931) These thunks can be accessed using `__impchk_*` symbols, though they are typically not called directly. Instead, they are used to populate the auxiliary IAT. When the imported function is x86_64 (or an ARM64EC function with a patched export thunk), the thunk is used to call it. Otherwise, the OS may replace the thunk at runtime with a direct pointer to the ARM64EC function to avoid the overhead.
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.