search for: ordinay

...compile. I've submitted several fixes for this in the past (against 2.6) [1], but this is very easy to regress given that valgrind memcheck will not detect this. The only way to detect is either continuously repeat compilation, and track deltas, as you've done; or tweak the source to use ordinay allocators instead of pool allocators (but this can't be done blindly, as in several cases LLVM code relies on the pool to managing the objective time lifetimes). Jose [1] I'd suggest you to try your sample against http://cgit.freedesktop.org/~jrfonseca/llvm/log/?h=backports_26 ----- Ori...

Hi, I put the sample code and a brief analysis using Valgrind to GitHub in order to make my problem clear. https://github.com/naosuke/how-to-free-memory-of-JIT-function The Valgrind heap profiler indicates memory leaking but I don't get what is wrong with the way to free memory. If someone could please offer some advice/suggestion on this, I would really appreciate it. Best, Naosuke On

Hi, I'm testing how to free memory of a JIT'd function. I thought ExecutionEngine::freeMachineCodeForFunction() and Function::eraseFromParent() would work and did a test with the following sample code. But I found that the memory usage of the process is constantly growing as the while loop goes. Could someone shed light on this please? Here is the code. int main(int argc, char **argv) {