??? 03/10/08 12:07 Read: times |
#152078 - High risk Responding to: ???'s previous message |
Christoph Franck said:
The compiler ... could keep the loop counter somewhere in data memory, or use a register... Absolutely: This is a key area where changing apparently "unrelated" code nearby could affect the timing! By changing apparently "unrelated" code nearby it is quite conceivable that you could affect the compiler's decision on what to place into registers... Again: You can never know the CPU cycle count of anything written in any HLL; eg, 'C'. |