SpritesMind.Net

Plus, when you have 4 bit fractions, you've got to implement that 'nasty' shift that I mentioned earlier. It really, really isn't worth limiting yourself when the code is no faster.

In fairness though, you wouldn't convert the number to its integer portion until you display the sprite on the ...

Well, my reply was in response to you saying that "4 times as many instructions executed" needed backup. I could have used a loop in my example, but I didn't, because although it would have looked shorter on paper, it would have been more instructions executed. I also pointed out that the 65816 ...

Well, my reply was in response to you saying that "4 times as many instructions executed" needed backup. I could have used a loop in my example, but I didn't, because although it would have looked shorter on paper, it would have been more instructions executed. I also pointed out that the 65816 ...

Which is exactly what I posted.

I'm not really sure if you're saying you posted execution or overall size when you say that. What I do know is that you've referred to several things as increasing instruction count that decrease execution time, like unrolling loops.

...No. I wouldn't have posted ...

When I was referring to code size I was referring to number of instructions executed, not number of instructions in a routine. For that to be a meaningful comparison you'd have to factor in instruction density which is totally different between the processors.

I don't think a 32bit add is a good ...

What are you talking about? I'm not deliberately misrepresenting anything. And I don't appreciate the implication.

Then quit misrepresenting things.

I was referring *just* to the number of cycles form the interrupt being trigger to the point in which the interrupt user routine starts ...