search for: __llvm_stackmaps

Displaying 8 results from an estimated 8 matches for "__llvm_stackmaps".

2018 Nov 05
2
ORC JIT api, object files and stackmaps
...I pass an ObjectFile saved in question#1 back to ORC so that it will relocate it and generate function pointers? (3) How do I get access to the relocated ObjectFile sections? Currently I subclass SectionMemoryManager and implement allocateDataSection(...) I can get the memory for the "__llvm_stackmaps" section - but I don't know when/if the contents have been fully set up with relocated function pointers. (4) For the "__llvm_stackmaps" section - will I need to do any relocation to obtain the function pointers? Background: I'm using llvm.experimental.stackmaps to register...
2015 Aug 09
2
About Stackmap section
...LLVMMemoryManagerAllocateDataSectionCallback(). When LLVM creates this section, it invokes the callback and passes the section name. The JIT can record the in-memory address of the section at this time and later parse it to recover the stack map data. On Darwin, the stack map section name is "__llvm_stackmaps". The segment name is "__LLVM_STACKMAPS"." However I can't figure how to make LLVMCreateSimpleMCJITMemoryManager or LLVMMemoryManagerAllocateDataSectionCallback or make use of them. And I could not find examples for their useage. Any help is appreciated. Regards, Marwa Yu...
2018 Nov 05
2
ORC JIT api, object files and stackmaps
...heers, Stefan Am 05.11.18 um 19:44 schrieb Christian Schafmeister via llvm-dev: > I think I found the answer to #3 and #4. > (a) I overloaded the SectionMemoryManager::finalizeMemory(...) method.  > (b) I first call the base classes method (maybe not necessary). > (c) At this point the __llvm_stackmaps section that I saved in thread > local memory when allocateDataSection was called appears to be fully > set up and relocated. > > > On Mon, Nov 5, 2018 at 12:36 PM Christian Schafmeister > <meister at temple.edu <mailto:meister at temple.edu>> wrote: > > I ha...
2018 May 29
0
Getting stack size of compiled functions from LLVM
On 5/28/2018 11:34 PM, Nicholas Chapman via llvm-dev wrote: > Hi all, > I'm trying to get the amount of stack memory used by the functions I > am JIT compiling with LLVM. > I have a host C++ program, and I want to be able to access the stack > size from the host C++ program. > > I see in PrologEpilogInserter.cpp that the computed stack size is read > from the
2018 May 29
2
Getting stack size of compiled functions from LLVM
Hi all, I'm trying to get the amount of stack memory used by the functions I am JIT compiling with LLVM. I have a host C++ program, and I want to be able to access the stack size from the host C++ program. I see in PrologEpilogInserter.cpp that the computed stack size is read from the MachineFunction corresponding to a Function, in order to issue a warning if the stack size is too large.
2017 Mar 04
2
Figuring out return address of a call
Hi folks, I'm trying to figure out the return address of a function in an LLVM pass, i.e., the byte address right after the end of the call instruction (so that I can initialize a global variable with the return address of a function for a sanity check). Due to some other constraints, I have to run this pass in somewhere in the midend. At a high level, I want to find the address after a call
2015 Apr 23
5
[LLVMdev] RFC: implicit null checks in llvm
..., otherwise it aborts. Note that the signal handler / runtime do not themselves raise exceptions at the ABI level (though they do so conceptually), but the landing pad block can raise one if it wants to. The table mapping load/store PCs to unwind PCs can be reported to the language runtime via an __llvm_stackmaps like section. I am strongly in favor of making this section as easy to parse as possible. # optimization pass to create invokes to @llvm.(load|store)_with_trap With the @llvm.(load|store)_with_trap intrinsics in place, we can write an LLVM pass that folds null checks into nearby memory operati...
2015 Apr 23
4
[LLVMdev] RFC: implicit null checks in llvm
...ler / runtime do not themselves raise > > exceptions at the ABI level (though they do so conceptually), but the > > landing pad block can raise one if it wants to. > > > > The table mapping load/store PCs to unwind PCs can be reported to the > > language runtime via an __llvm_stackmaps like section. I am strongly > > in favor of making this section as easy to parse as possible. > > Let’s just be clear that it is not recommended for the frontend to produce > these intrinsics. They are a compiler backend convenience. (I don’t want > InstCombine or any other stand...