[ORC] Align GDB-JIT alloc-action names with the ORC runtime (#216024) Align LLVM's GDB-JIT registration alloc-action names with the names added to the ORC runtime in 4a0fdbc25bb, and add a name for the deregistration action. Look these names up in the Bootstrap JITDylib rather than the Process JITDylib. Since the lookup no longer depends on process symbols, drop the "requires process symbols" preconditions guarding MachO debugger support in llvm-jitlink and enableDebuggerSupport. GDBJITDebugInfoRegistrationPlugin::Create also loses its Triple parameter, which is now unused. Together this lets GDBJITDebugInfoRegistrationPlugin work against either the LLVM OrcTargetProcess or ORC runtime implementation of these actions.
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.