[offload][omp] Load and resolve device binaries through liboffload Migrate DeviceTy::loadBinary and global/kernel symbol resolution off GenericPluginTy::load_binary/get_global/get_function onto liboffload's Program/Symbol API, encapsulated in a new ProgramTy abstraction that wraps an ol_program_handle_t. Kernel symbol resolution still needs the plugin's opaque GenericKernelTy* handle for the legacy launch path, obtained via a temporary __ol_tgt_GetKernelFromSymbol helper rather than new public liboffload API surface. Removes the now-dead __tgt_device_binary type and the corresponding GenericPluginTy methods and exports entries.
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.