search for: needstoreserveallocationspace

...at-or-before reserveAllocationSpace, is conceptually similar to registerEHFrames in that it's reserving EH frames, but that additionally needs to separate out the per-function information. A few options come to mind: 1. Add a needsToReserveEHFrames callback on MemoryManager (to parallel needsToReserveAllocationSpace), and a reserveEHFrames callback (parallel to registerEHFrames) that the loader would use to notify the memory manager if needsToReserveEHFrames() is true. This seems at a high-level the most straightforward fit for the LLILC requirement, but I don't know if for other targets it would even be...

...at-or-before reserveAllocationSpace, is conceptually similar to registerEHFrames in that it's reserving EH frames, but that additionally needs to separate out the per-function information. A few options come to mind: 1. Add a needsToReserveEHFrames callback on MemoryManager (to parallel needsToReserveAllocationSpace), and a reserveEHFrames callback (parallel to registerEHFrames) that the loader would use to notify the memory manager if needsToReserveEHFrames() is true. This seems at a high-level the most straightforward fit for the LLILC requirement, but I don't know if for other targets it would even be...

...; conceptually similar to registerEHFrames in that it's reserving EH frames, > but that additionally needs to separate out the per-function information. > > > > A few options come to mind: > > 1. Add a needsToReserveEHFrames callback on MemoryManager (to > parallel needsToReserveAllocationSpace), and a reserveEHFrames callback > (parallel to registerEHFrames) that the loader would use to notify the > memory manager if needsToReserveEHFrames() is true. This seems at a > high-level the most straightforward fit for the LLILC requirement, but I > don't know if for other targe...

Hi Bjoern, For single object files you can override the needsToReserveAllocationSpace method that is inherited from llvm::RuntimeDyld::MemoryManager (make it return true) and then implement the reserveAllocationSpace method to allocate memory for all sections up front. There is no easy way to do this for multiple object files. I think you would have to mimic the memory size calcul...

...at-or-before reserveAllocationSpace, is conceptually similar to registerEHFrames in that it's reserving EH frames, but that additionally needs to separate out the per-function information. A few options come to mind: 1. Add a needsToReserveEHFrames callback on MemoryManager (to parallel needsToReserveAllocationSpace), and a reserveEHFrames callback (parallel to registerEHFrames) that the loader would use to notify the memory manager if needsToReserveEHFrames() is true. This seems at a high-level the most straightforward fit for the LLILC requirement, but I don't know if for other targets it would even be...

...at-or-before reserveAllocationSpace, is conceptually similar to registerEHFrames in that it's reserving EH frames, but that additionally needs to separate out the per-function information. A few options come to mind: 1. Add a needsToReserveEHFrames callback on MemoryManager (to parallel needsToReserveAllocationSpace), and a reserveEHFrames callback (parallel to registerEHFrames) that the loader would use to notify the memory manager if needsToReserveEHFrames() is true. This seems at a high-level the most straightforward fit for the LLILC requirement, but I don't know if for other targets it would even be...

...at-or-before reserveAllocationSpace, is conceptually similar to registerEHFrames in that it's reserving EH frames, but that additionally needs to separate out the per-function information. A few options come to mind: 1. Add a needsToReserveEHFrames callback on MemoryManager (to parallel needsToReserveAllocationSpace), and a reserveEHFrames callback (parallel to registerEHFrames) that the loader would use to notify the memory manager if needsToReserveEHFrames() is true. This seems at a high-level the most straightforward fit for the LLILC requirement, but I don't know if for other targets it would even be...

Hello everyone, I want to use the LLVM to write a JIT client, that works with shared memory. Currently I proceed as following: I wrote an own class that inherits "RTDyldMemoryManager". The functions "allocateCodeSection" and "allocateDataSection" are allocating local non-shared memory. I store there addresses in a std::vector. When the function