Skip to content
Prev 36499 / 63424 Next

suggestion how to use memcpy in duplicate.c

On Apr 21, 2010, at 4:13 PM, Romain Francois wrote:

            
Nope, since everything involved is loop invariant so the pointer values don't change (you'd have to declare s or t volatile to prevent that).

Try using gcc -s and you'll see that the code is the same (depending on the version of gcc the order of the first comparison can change so technically the INTEGER(x) version can save one add instruction in the degenerate case and be faster(!) in old gcc).

Cheers,
Simon