On 19.02.2018 10:25, Anton Shepelev wrote:
However I think, FPC should generate the profiling
code itself. Then there is no need to modify the
code before and after the compilation.
Not, I think, for the naive light-weight profiling
that FPProfiler offers. Its functionality is easily
decoupled from that of the compiler and I think
should stay so, for better modularity.
I agree with Simon here. It's a similar scenario like heaptrc. Why not
to add a compiler parameter to include profiling info? That would be
fpc-devel maillist - email@example.com