Filip Pizlo 7aa695e026 This threads SectionName through the allocateCodeSection/allocateDataSection APIs, both in C++ and C land. ... 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		2013-10-02 00:59:25 +00:00
..
CMakeLists.txt	Remove exception handling support from the old JIT.	2013-05-07 20:53:59 +00:00
JIT.cpp	Fix the build issue under ia64. Close bug #5715	2013-08-27 06:49:46 +00:00
JIT.h	Move getPointerToNamedFunction() from JIT/MCJIT to JITMemoryManager.	2012-03-28 21:46:36 +00:00
JITEmitter.cpp	Remove dead code.	2013-05-10 23:34:51 +00:00
JITMemoryManager.cpp	This threads SectionName through the allocateCodeSection/allocateDataSection APIs, both in C++ and C land.	2013-10-02 00:59:25 +00:00
LLVMBuild.txt	LLVMBuild: Remove trailing newline, which irked me.	2011-12-12 19:48:00 +00:00
Makefile	…