Probably some of the leaks Valgrind reports are spurious, but the numbers
seem to be significant enough to demand some attention:
==10132== LEAK SUMMARY:
==10132== definitely lost: 15,624 bytes in 558 blocks.
==10132== indirectly lost: 44,548 bytes in 1,591 blocks.
==10132== possibly lost: 37,576 bytes in 98 blocks.
==10132== still reachable: 1,336,876 bytes in 1,364 blocks.
==10132== suppressed: 0 bytes in 0 blocks.
I know that a patch would be more appreciated, but I still don’t feel
confident enough to fiddle with the LLVM core… Could anyone
take a look at the report and try fix the leaks?
==10132== Memcheck, a memory error detector.
==10132== Copyright (C) 2002-2005, and GNU GPL’d, by Julian Seward et al.
==10132== Using LibVEX rev 1575, a library for dynamic binary translation.
==10132== Copyright (C) 2004-2005, and GNU GPL’d, by OpenWorks LLP.
==10132== Using valgrind-3.1.1, a dynamic binary instrumentation framework.
==10132== Copyright (C) 2000-2005, and GNU GPL’d, by Julian Seward et al.
==10132== For more details, rerun with: -v