Summary: One of the main disadvantages to using the RPC interface is that it requires a server thread to spin on the mailboxes checking for work. The vast majority of the time, there will be no work and work will come in large bursts. The HSA / KFD interface supports device-side interrupts and already has handling for binding these events to an HSA signal. This means that we can send interrupts from the GPU to wake a sleeping thread on the CPU. The sleeping thread will be descheduled with a blocking HSA wait call and woken up when its event ID is raised through the kernel driver's interrupt. This is very target-specific handling, but I believe it is valuable enough to warrant it being in the protocol. It is completely optional, as it is ignored if uninitialized. This should bring this support at parity with the interface HIP expects.
export module foo not following a semicolon and there are no rest pp-tokens in current module file (#187845)
The LLVM Compiler Infrastructure
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.
Getting the Source Code and Building LLVM
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.
Getting in touch
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.