| commit | 85c649bc02a6605f541b09b33a200a78275ed90f | [log] [tgz] |
|---|---|---|
| author | Lang Hames <lhames@gmail.com> | Mon Apr 17 15:26:28 2023 +0000 |
| committer | Lang Hames <lhames@gmail.com> | Mon Apr 17 16:41:00 2023 +0000 |
| tree | 78b587cd6fea1fdd69eb63b149b9f66b9c62ab80 | |
| parent | 2cd15925f4485fc618bc33c1337e1b6f63d84ef6 [diff] |
[ORC][LLJIT] Use JITLink by default on ELF/x86-64. This patch switches LLJIT's default JIT linker for ELF/x86-64 from RuntimeDyld to JITLink. Most clients should not be affected, but if you were explicitly accessing the old RTDyldObjectLinkingLayer (e.g. to install JITEventListeners) you will need to either force use of RuntimeDyld (following the example in llvm/examples/OrcV2Examples/LLJITWithCustomObjectLinkingLayer), or switch to using JITLink plugins instead.
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, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.