> No. The only thing we support is a recursive malloc as seen in: > ./gcc/testsuite/gcc.dg/tree-prof/indir-call-prof-malloc.c > > It was added in g:bc2b1a232b1825b421a1aaa21a0865b2d1e4e08c as we use a > statically allocated buffer when we recursively entry allocate_gcov_kvp. > > However this is different as we can't call malloc/calloc from the function as > we're in code that initializes a memory allocator. > > We can mitigate the issue with a pair of new functions __gcov_supress_malloc > and __gcov_alloc_malloc that will be called by a custom memory allocator. > > What do you think about it?
How this works with the llvm implementation (that is very similar here, right?) Honza
