[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inline asm?

Joel Stanley wrote:

> > Remember
> >   2) Analize where the code is too slow before optimizing.
> > It sucks to optimize the wrong function.  I know.
> Heh. I take it that this is the "art more than science" part?
> How does what determine where the code is too slow? Line-by-line analysis?

Compile your stuff with the -pg option to gcc/g++/egcs/c++ and later
check out the data it created with the gprof program (the GNU profiler).
This is very helpful!

Pierre Phaneuf
Ludus Design, http://ludusdesign.com/
"First they ignore you. Then they laugh at you.
Then they fight you. Then you win." -- Gandhi