search for: pr23991

Displaying 2 results from an estimated 2 matches for "pr23991".

Did you mean: pr20997
2016 May 24
2
ORC and MCJIT clients: Heads up, API breaking changes in the pipeline.
...sponsible for freeing the memory that they've allocated when they are destructed. To transition, clients should track the frames registered by their class, then deregister them in the destructor. For in-tree memory managers (and RuntimeDyld itself) this bug is being tracked by https://llvm.org/PR23991 . 3) Some operations in the ORC APIs, RuntimeDyld, SymbolResolver and MemoryManager will be modified to return Error/Expected. MCJIT and ORC both support remote execution of JIT'd code via RPC, but there is currently no way to cleanly bail out and report failure in the case of an RPC error. A...
2016 May 27
1
ORC and MCJIT clients: Heads up, API breaking changes in the pipeline.
...memory that they've allocated when they are destructed. > > To transition, clients should track the frames registered by their > class, then deregister them in the destructor. For in-tree memory > managers (and RuntimeDyld itself) this bug is being tracked > by https://llvm.org/PR23991 . > > 3) Some operations in the ORC APIs, RuntimeDyld, SymbolResolver and > MemoryManager will be modified to return Error/Expected. > > MCJIT and ORC both support remote execution of JIT'd code via RPC, but > there is currently no way to cleanly bail out and report failure in...