🚀 go-pugleaf

Eddy Vluggen wrote:

> Don't call 16bit routines or use 16 bit DLL's. Any good with C++? Put much
> used functions in a .OBJ file, and bind it into your program. Or even
> better, find an assembler guru!

It's not that easy. If you are using a pentium cpu, simply clock
cycle counting won't help because certain instructions can be
performed simultaneously. The guys at Borland who write the
compilers know what code to generate to obtain fastest executables.

The other day I spent my time to convert 3 lines of pascal code into
more than 50 lines of highly optimized assembler code avoiding slow
commands as loops, jumps, calls, and pushs, and it ended up in
taking 5 per cent _more_ cpu time than the compiler generated code.

A hint that hasn't been given yet might be helpful:
sometimes you often have to call a function that takes a lot of time.
If there are only a small amount of values that are passed to that
function then you can precalculate all the results and store them
in an array to fetch them when needed.
That's what a pentium does internally when executing a DIV instruction.

Klaus