Just to add to this, in C, a for-loop is smaller but less optimized than writing out each statement seperately.
And using cos() or other trig functions might be smaller but a lookup table is much faster.
When you're not specifically dealing with instructions, code size doesn't really have any correlation to speed.
Rich | [reply] |
Just to beat a dead horse:
in C, a for-loop is smaller but less optimized than writing out each statement seperately.
...unless the unrolled loop's extra code size causes a
cache miss across a slow bus, in which case the for-loop is
more optimized (assuming, of course, that the loop fits in
a cache line).
--
F
o
x
t
r
o
t
U
n
i
f
o
r
m
Found a typo in this node? /msg me
% man 3 strfry
| [reply] |
| [reply] |