Support orc runtime and use it to enhance support of x86_64-windows-msvc target.
Details
Diff Detail
Event Timeline
clang/tools/clang-repl/ClangRepl.cpp | ||
---|---|---|
119 | Do we want to sink this in clang::Interpreter::create. This way other users would just use it straight out of the box? Maybe we can add a default argument useOrcRuntimeIfSupported = true in case things are not yet very stable. |
clang/lib/Interpreter/IncrementalExecutor.cpp | ||
---|---|---|
63–72 | This code will never be executed. Or am I missing something? |
clang/lib/Interpreter/IncrementalExecutor.cpp | ||
---|---|---|
63–72 | That's definitely a non-obvious one. The lambda ends up in the builder states' CreateObjectLinkingLayer member and gets called from LLJIT: https://github.com/llvm/llvm-project/blob/release/15.x/llvm/lib/ExecutionEngine/Orc/LLJIT.cpp#L736 What's interesting is the EPC capture: In fact, it's a pointer so we wouldn't want the &. However, instead of capturing EPC, it might be easier to just obtain it inside the lambda via ES->getExecutorProcessControl(). |
This code will never be executed. Or am I missing something?