We should remove all profiling from the code.

[GoogleCodeExporter]

At some point someone was using profiling methods to optimize the code. I 
respect this. This is only one right way to do this. But there are tools that 
will do much better job.

Like gprof or callgrind.

I do not see any good reason to keep profiling module in the code because we 
can get such a nice pictures as attached, without using this module.

Less code => less chances for a bug.

Original issue reported on code.google.com by iglovi...@gmail.com on 5 Jan 2014 at 8:53

Attachments:

• time_dependent.png
• time_independent.png

[GoogleCodeExporter]

Those routines were designed for profiling GPU performance, and, as far as I 
know (perhaps I'm wrong), gprof alone cannot profile programs running on GPU. 
Now that the GPU project is done, I think we can remove those parts.

Original comment by cxc639 on 9 Feb 2014 at 12:47