5602b98193
A controller call's on-complete handler may run managed code, so it must be dispatched by the Session under a ManagedCodeTaskGroup token, not invoked directly by the ControllerAccess (which previously held it as a plain callable and called it itself -- untokened and undispatched). Wrap it in an opaque ControllerAccess::OnControllerCallReturn that implementations can hold but not call. They complete it via exactly one of three Session-provided paths: - handleControllerCallResult -- the controller returned a result; dispatches the handler under a fresh token. Asserts the managed-code group is still open (i.e. before notifyDisconnected). - failPendingControllerCall -- an already-enqueued call is failed because the connection dropped before a result arrived (the disconnect drain); dispatches the handler under a token with a disconnect error. - failControllerCallInline -- a call made from within callController while already disconnecting, which can never be enqueued; runs the handler inline with a disconnect error, where the caller (and its token) is still on the stack. Together these guarantee a controller call's handler always runs exactly once, with a result or a disconnect error, and never runs managed code without a token. Only the success path takes a result value; the two failure paths produce the canonical disconnect error internally, so it can't be gotten wrong. InProcessControllerAccess and the Session unit tests are updated. |
||
|---|---|---|
| .ci | ||
| .github | ||
| bolt | ||
| clang | ||
| clang-tools-extra | ||
| cmake | ||
| compiler-rt | ||
| cross-project-tests | ||
| flang | ||
| flang-rt | ||
| libc | ||
| libclc | ||
| libcxx | ||
| libcxxabi | ||
| libsycl | ||
| libunwind | ||
| lld | ||
| lldb | ||
| llvm | ||
| llvm-libgcc | ||
| mlir | ||
| offload | ||
| openmp | ||
| orc-rt | ||
| polly | ||
| runtimes | ||
| third-party | ||
| utils | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .clang-tidy | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE.TXT | ||
| pyproject.toml | ||
| README.md | ||
| SECURITY.md | ||
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.