>>3
They're faster than for loops, but a lot of compilers don't support them. If you pass -funroll-loops to gcc when compiling, it will convert all of your for loops to unroll loops automatically.
I always use this flag. I don't know why anyone would want to have for loops in their executable files when unroll loops are available for the mere cost of a simple compiler flag.