search for: reserveallocationspace

...extracted from the MSIL method). The CoreCLR requires the jit to notify it of the size of the unwind info descriptors for each function in the module before reserving the memory it will be loaded into. So we need a call (or calls) from the Jit/loader into the MemoryManager that runs 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...

...extracted from the MSIL method). The CoreCLR requires the jit to notify it of the size of the unwind info descriptors for each function in the module before reserving the memory it will be loaded into. So we need a call (or calls) from the Jit/loader into the MemoryManager that runs 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...

...IL method). The CoreCLR > requires the jit to notify it of the size of the unwind info descriptors > for each function in the module *before* reserving the memory it will be > loaded into. So we need a call (or calls) from the Jit/loader into the > MemoryManager that runs 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 > p...

...extracted from the MSIL method). The CoreCLR requires the jit to notify it of the size of the unwind info descriptors for each function in the module before reserving the memory it will be loaded into. So we need a call (or calls) from the Jit/loader into the MemoryManager that runs 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...

...extracted from the MSIL method). The CoreCLR requires the jit to notify it of the size of the unwind info descriptors for each function in the module before reserving the memory it will be loaded into. So we need a call (or calls) from the Jit/loader into the MemoryManager that runs 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...

...extracted from the MSIL method). The CoreCLR requires the jit to notify it of the size of the unwind info descriptors for each function in the module before reserving the memory it will be loaded into. So we need a call (or calls) from the Jit/loader into the MemoryManager that runs 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...

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...

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