This will let ORC JIT clients plug in custom logic for the mmap, munmap and
mprotect paths.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Out of interest, what’s the use case for this? I’d have expected sys::Memory to be good enough for block-based allocation (though there’s the known issue with PaX on BSD that I need to fix), and using a non block-based underlying allocator seems like it’d risk unnecessary fragmentation.
Comment Actions
This is just so that the mmap can come from a file or a memfd, which will make the mapping show up with a name and not as "anon" under perf etc.
Comment Actions
LGTM.
include/llvm/ExecutionEngine/SectionMemoryManager.h | ||
---|---|---|
73 ↗ | (On Diff #120283) | Remove "is". |
Comment Actions
Ahh. Makes sense.
Apologies for the delayed reply: I've been on the road. Thanks asbirlea and jlebar for stepping in.