   Cycles->Motolora HC11 68000....Win32?
  If anyone reading this post is familar with the documentation of the motorola processors, you know you can match the instruction used with the number of cycles used. If your E-Clock Frequency if 4.9512MHz for example, divided by 40 and inversed to find the time it takes for one cycle to execute = 813.8ns. I want a way to relate even C++ syntax, or low-level Win32 Assembly Syntax to relate to the same, I''m asking for a resource to reference to... For optimization purposes, i''m sure I won''t be the only one looking forward to this, please let me know!!-CarandiruDirectX 9 / C++ Graphics Engine Programmer 
  Ah, the old 68000 processor, how i loved her back on my STe, counting clock cycles and bashing the hardware with my DevPac assembler... *wipes away a happy tear*however, its not as easy at that on other processors, a processor (AMD or Intel) can decode and execute muplitple instructions at once, it can even reorder instructions to better help the execution, so you cant say that if one instruction takes X clock cycle then 3 will take 3X because the rules change, for example 3 mov instructions, taking 2 cycles each could, in theory, be decoded pretty much at the same time, so instead of 6 cycles to execute it would only take 3.At best you could probably get a rough guide from the chip makers, and that might help you estimate things, but it wont be spot on.. As for relating C++ to clock cycles, pretty much impossible, simple because you dont know how the compiler will deal with it when it ends up as machine code ;  thank you, I don''t know why I asked about how to compare c++ to clock cycles, considering the compiler optimization''s. ;P, nevertheless just curious! ;  The number of cycles use by each instruction is specified in the processor datasheet, which you can download from the Motorola site.  The HC11 doesn''t pipeline as far as I know, so it''s fairly easy to time stuff if you do it in ASM.;  Z80, 68000, 68HC11...That''s pure love right there... ;  I never thought I would say that assembly actually is fun, but it is on the 68K. Really cool to write 1337 programz like a pong game displayed on five LEDs. ;  I loved the 6809 until I had to do floating point math :-) 