37ed9c199ca639565f6ce88105f9e39e898d82d0 |
|
01-Dec-2014 |
Stephen Hines <srhines@google.com> |
Update aosp/master LLVM for rebase to r222494. Change-Id: Ic787f5e0124df789bd26f3f24680f45e678eef2d
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
c6a4f5e819217e1e12c458aed8e7b122e23a3a58 |
|
21-Jul-2014 |
Stephen Hines <srhines@google.com> |
Update LLVM for rebase to r212749. Includes a cherry-pick of: r212948 - fixes a small issue with atomic calls Change-Id: Ib97bd980b59f18142a69506400911a6009d9df18
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
36b56886974eae4f9c5ebc96befd3e7bfe5de338 |
|
24-Apr-2014 |
Stephen Hines <srhines@google.com> |
Update to LLVM 3.5a. Change-Id: Ifadecab779f128e62e430c2b4f6ddd84953ed617
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
6eb43d295625cd2ff314c59b49d4fd11f3348cad |
|
02-Oct-2013 |
Filip Pizlo <fpizlo@apple.com> |
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
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
60808c76b4f3674a08fd468bcb5afb2cab77227a |
|
14-Jul-2013 |
Stephen Lin <stephenwlin@gmail.com> |
Convert Windows to Unix line endings, no functionality change. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@186264 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
abb38fe8dec11b1ea7535f84fac8ad0f0af70add |
|
17-May-2013 |
David Tweed <david.tweed@arm.com> |
Minor changes to the MCJITTest unittests to use the correct API for finalizing the JIT object (including XFAIL an ARM test that now needs fixing). Also renames internal function for consistency. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182085 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
5a88dda4be791426ab4d20a6a6c9c65d66614a27 |
|
04-Dec-2012 |
Chandler Carruth <chandlerc@gmail.com> |
Sort the #include lines for unittest/... git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@169250 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|
927ba6a0b36b8219955a657545fcb1c863734993 |
|
27-Nov-2012 |
Andrew Kaylor <andrew.kaylor@intel.com> |
Moving SectionMemoryManager into RuntimeDyld and adding unit tests for it. The SectionMemoryManager now supports (and requires) applying section-specific page permissions. Clients using this memory manager must call either MCJIT::finalizeObject() or SectionMemoryManager::applyPermissions() before executing JITed code. See r168718 for changes from the previous implementation. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168721 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/unittests/ExecutionEngine/MCJIT/MCJITMemoryManagerTest.cpp
|