diff options
| author | Lang Hames <lhames@gmail.com> | 2015-03-31 20:31:14 +0000 |
|---|---|---|
| committer | Lang Hames <lhames@gmail.com> | 2015-03-31 20:31:14 +0000 |
| commit | 3dac3f7fe6e541980fdd4d3fb9575107cbc74c19 (patch) | |
| tree | 99ccf7b4ab37da4053f610ab2483e034fc4ff2ef /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp | |
| parent | b99d9a0a816bf8a9e3cce1c6ccba099669ac1e62 (diff) | |
| download | llvm-3dac3f7fe6e541980fdd4d3fb9575107cbc74c19.zip llvm-3dac3f7fe6e541980fdd4d3fb9575107cbc74c19.tar.gz llvm-3dac3f7fe6e541980fdd4d3fb9575107cbc74c19.tar.bz2 | |
[ExecutionEngine] Fix MCJIT::addGlobalMapping.
This patch fixes MCJIT::addGlobalMapping by changing the implementation of the
ExecutionEngineState class. The new implementation maintains a bidirectional
mapping between symbol names (std::strings) and addresses (uint64_ts), rather
than a mapping between Value*s and void*s.
This has fix has been made for backwards compatibility, however the strongly
preferred way to resolve unknown symbols is by writing a custom
RuntimeDyld::SymbolResolver (formerly RTDyldMemoryManager) and overriding the
findSymbol method. The addGlobalMapping method is a hangover from the legacy JIT
(which has was removed in 3.6), and may be deprecated in a future release as
part of a clean-up of the ExecutionEngine interface.
Patch by Murat Bolat. Thanks Murat!
llvm-svn: 233747
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp')
0 files changed, 0 insertions, 0 deletions