I feel thye calling of assembler... I''m not sure why, I guess it just that last great programming challenge. My code is sprinkled with hunks of ''optimised'' code I''ve collected from various sources. Problem is: - I can''t read them.. - I can''t determine whether they are actually faster. - I don''t know how to count the clock cycles it takes to determin if something _should_ even be optimised. I''ve started reading the Gamedev tutorials, while their more suited towards top to bottom assembler I''m still finding them useful. The other day I found a bunch of math functions in assembler that has the number of ''clock'' each bit took. How do you determine this? Being able to measure processing requirements I think would be the first step in deciding when to optimise....? gimp

you might want to try www.intel.com.

this link here is to the intel 80x86 instruction set with timings and detailed information about every intruction.

http://developer.intel.com/design/pentium/manuals/24319101.pdf

hope this helps.

ahhhhhh!

I was thinking that there was some kind of timer function you used to measure it... Thanks!