llvm-project.git/llvm/lib/ExecutionEngine/MCJIT/SectionMemoryManager.cpp, branch users/nico/python-1

[Orc] Move SectionMemoryManager's implementation from MCJIT to ExecutionEngine.

2015-02-06T19:36:40+00:00

This is a more sensible home for SectionMemoryManager, and allows the implementation
to be shared between Orc and MCJIT.

llvm-svn: 228427

Don't use 'using std::error_code' in include/llvm.

2014-06-12T21:46:39+00:00

This should make sure that most new uses use the std prefix.

llvm-svn: 210835

Use error_code() instead of error_code::succes()

2014-05-31T01:37:45+00:00

There is no std::error_code::success, so this removes much of the noise
in transitioning to std::error_code.

llvm-svn: 209952

[C++] Use 'nullptr'.

2014-04-24T06:44:33+00:00

llvm-svn: 207083

Fix known typos

2014-01-24T17:20:08+00:00

Sweep the codebase for common typos. Includes some changes to visible function
names that were misspelt.

llvm-svn: 200018

This threads SectionName through the allocateCodeSection/allocateDataSection APIs, both in C++ and C land.

2013-10-02T00:59:25+00:00

It's useful for the memory managers that are allocating a section to know what the name of the section is.  
At a minimum, this is useful for low-level debugging - it's customary for JITs to be able to tell you what 
memory they allocated, and as part of any such dump, they should be able to tell you some meta-data about 
what each allocation is for.  This allows clients that supply their own memory managers to do this.  
Additionally, we also envision the SectionName being useful for passing meta-data from within LLVM to an LLVM 
client.

This changes both the C and C++ APIs, and all of the clients of those APIs within LLVM.  I'm assuming that 
it's safe to change the C++ API because that API is allowed to change.  I'm assuming that it's safe to change 
the C API because we haven't shipped the API in a release yet (LLVM 3.3 doesn't include the MCJIT memory 
management C API).

llvm-svn: 191804

Adding multiple module support for MCJIT.

2013-10-01T01:47:35+00:00

Tests to follow.

PIC with small code model and  EH frame handling will not work with multiple modules.  There are also some rough edges to be smoothed out for remote target support.

llvm-svn: 191722

Put RTDyldMemoryManager into its own file, and make it linked into

2013-05-21T20:24:07+00:00

libExecutionEngine. Move method implementations that aren't specific to 
allocation out of SectionMemoryManager and into RTDyldMemoryManager.

This is in preparation for exposing RTDyldMemoryManager through the C 
API.

This is a fixed version of r182407 and r182411. That first revision 
broke builds because I forgot to move the conditional includes of 
various POSIX headers from SectionMemoryManager into 
RTDyldMemoryManager. Those includes are necessary because of how 
getPointerToNamedFunction works around the glibc libc_nonshared.a thing. 
The latter revision still broke things because I forgot to include 
llvm/Config/config.h.

llvm-svn: 182418

Roll out r182411 and 182412 because it's still broken.

2013-05-21T20:17:14+00:00

llvm-svn: 182415

Put RTDyldMemoryManager into its own file, and make it linked into

2013-05-21T20:07:12+00:00

libExecutionEngine. Move method implementations that aren't specific to 
allocation out of SectionMemoryManager and into RTDyldMemoryManager.

This is in preparation for exposing RTDyldMemoryManager through the C 
API.

This is a fixed version of r182407. That revision broke builds because I 
forgot to move the conditional includes of various POSIX headers from 
SectionMemoryManager into RTDyldMemoryManager. Those includes are 
necessary because of how getPointerToNamedFunction works around the 
glibc libc_nonshared.a thing.

llvm-svn: 182411