25 Mar
2009
25 Mar
'09
4:42 a.m.
Hi, your post gave me the idea to profile the memory usage of the generated binary with valgrind.
Has there been an effort in jhc to reduce the memory footprint of generated code?
In this release of jhc, the problem is handled in a quite radical way. It seems that no free() is ever emitted, the allocated heap memory is not released. Well, this classifies like a bug, I guess. On the bright side, when I removed all memory deallocation from the C version, supposing (naively maybe) that it would radicaly reduce the difference in performance, jhc's still ran twice faster. Sylvain Nahas