diff options
author | Filip Pizlo <fpizlo@apple.com> | 2013-10-02 00:59:25 +0000 |
---|---|---|
committer | Filip Pizlo <fpizlo@apple.com> | 2013-10-02 00:59:25 +0000 |
commit | 6eb43d295625cd2ff314c59b49d4fd11f3348cad (patch) | |
tree | daec0d82ea11d026745a572949f7c7c1e6e8d5c0 /projects | |
parent | 2b53089bd017139f0125b870ace94ff27dffd2ff (diff) | |
download | external_llvm-6eb43d295625cd2ff314c59b49d4fd11f3348cad.zip external_llvm-6eb43d295625cd2ff314c59b49d4fd11f3348cad.tar.gz external_llvm-6eb43d295625cd2ff314c59b49d4fd11f3348cad.tar.bz2 |
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).
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@191804 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'projects')
0 files changed, 0 insertions, 0 deletions