> For short EX MVC's the burden of getting stuff in the right registers > makes MVCL less interesting.
As I understand it, and doesn't seem to have been mentioned, the big effect on EX has to do with caching. I believe that it should be near code and not data. (That is, it goes into the instruction cache instead of the data cache.) Then again, I could have that backwards. Other than cache, it should be plenty fast enough. > My preoccupation with this is mostly on Friday ;-) And I guess I > should not write real code on Friday 13th anyway... > The EX CLC is in fact in loop scanning a linked list for the right > entry among 100-200 elements. My big savings were moving the TRT etc > out of the loop. I was tempted to also take the decision between CLC > and EX CLC out of the loop, but didn't for ease of maintenance. I usually use a hash table. Especially if speed is important. You could also do binary search, which will find the right entry with about log(n) comparisons. -- glen
