llvm-project.git/llvm/examples/OrcV2Examples/LLJITWithObjectLinkingLayerPlugin/LLJITWithObjectLinkingLayerPlugin.cpp, branch users/nico/python-2

[ORC] Drop unused LinkGraphLinkingLayer::Plugin::notifyLoaded method. (#145457)

2025-06-24T09:00:24+00:00

This method was included in the original Plugin API as a counterpart to
JITEventListener::notifyLoaded but was never used.

Re-apply "[ORC] Remove the Triple argument from LLJITBuilder::..." with fixes.

2025-03-06T06:17:05+00:00

This re-applies f905bf3e1ef860c4d6fe67fb64901b6bbe698a91, which was reverted in
c861c1a046eb8c1e546a8767e0010904a3c8c385 due to compiler errors, with a fix for
MLIR.

Revert "[ORC] Remove the Triple argument from LLJITBuilder::ObjectLinking..."

2025-03-06T05:22:39+00:00

This reverts commit f905bf3e1ef860c4d6fe67fb64901b6bbe698a91 while I fix
some compile errors reported on the buildbots (see e.g.
https://lab.llvm.org/buildbot/#/builders/53/builds/13369).

[ORC] Remove the Triple argument from LLJITBuilder::ObjectLinkingLayerCreator.

2025-03-06T05:13:10+00:00

ExecutionSession can provide the Triple, so this argument has been redundant
for a while, and no in-tree clients use it.

Re-apply "[ORC] LLJIT updates: ExecutorNativePlatform, default ..." with fixes.

2023-04-08T02:40:58+00:00

This reapplies 371cb1af61d, which was reverted in 0b2240eda01 due to bot
failures.

The clang-repl test failure is fixed by dropping the process symbols definition
generator that was manually attached to the main JITDylib, since LLJIT now
exposes process symbols by default. (The bug was triggered when JIT'd code used
the process atexit provided by the generator, rather than the JIT atexit which
has been moved into the platform JITDylib).

Any LLJIT clients that see crashes in static destructors should likewise remove
any process symbol generators attached to their main JITDylib.

[ORC] Add JITDylib argument to ResourceManager notify-removing/transferring ops.

2022-12-19T22:56:08+00:00

In some cases it's helpful to group trackers by JITDylib. E.g. Platform classes
may want to track initializer symbols with a `JITDylib -> Tracker -> [ Symbol ]`
map. This makes it easy to collect all symbols for the JITDylib, while still
allowing efficient removal of a single tracker. Passing the JITDylib as an
argument to ResourceManager::notifyRemovingResources and
ResourceManager::notifyTransferringResources supports such use-cases.

[examples] Fix deprecated use of llvm::empty.

2022-10-10T05:00:43+00:00

Remove unneeded cl::ZeroOrMore for cl::opt options

2022-06-04T07:10:42+00:00

Similar to 557efc9a8b68628c2c944678c6471dac30ed9e8e.
This commit handles options where cl::ZeroOrMore is more than one line below
cl::opt.

[ORC] Return ExecutorAddrs rather than JITEvaluatedSymbols from LLJIT::lookup.

2022-05-05T20:56:00+00:00

Clients don't care about linkage, and ExecutorAddr is much more ergonomic.

Re-apply "[JITLink] Update JITLink to use ExecutorAddr rather... " with fixes.

2022-01-06T06:22:21+00:00

This re-applies 133f86e95492b2a00b944e070878424cfa73f87c, which was reverted in
c5965a411c635106a47738b8d2e24db822b7416f while I investigated bot failures.

The original failure contained an arithmetic conversion think-o (on line 419 of
EHFrameSupport.cpp) that could cause failures on 32-bit platforms. The issue
should be fixed in this patch.