summaryrefslogtreecommitdiffstats
path: root/clang/lib/CodeGen/CodeGenFunction.cpp
diff options
context:
space:
mode:
authorFilip Pizlo <fpizlo@apple.com>2013-10-02 00:59:25 +0000
committerFilip Pizlo <fpizlo@apple.com>2013-10-02 00:59:25 +0000
commit7aa695e0265727af08932d555d2303463eb8c17a (patch)
tree3af213e64b510f1ea8a37c0d1b7d3a48aa891606 /clang/lib/CodeGen/CodeGenFunction.cpp
parentf2dd4ef157a054301337d44edda3a1f3c2f4d8f9 (diff)
downloadbcm5719-llvm-7aa695e0265727af08932d555d2303463eb8c17a.tar.gz
bcm5719-llvm-7aa695e0265727af08932d555d2303463eb8c17a.zip
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
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud