HOW DOES I OPTIMIZE FURTHER AND UNROLL LOOPS

HOW?

I've never heard of a further loop.

And I've never heard of an unroll loop.

>>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.

>>4
ITS A CLASSIC TIME/SPACE TRADE-OFF

>>5
Actually I's not as simple, as smaller somethimes means faster (better branch prediction and less code cache pressure).

>>6
How exactly would smaller code benefit branch prediction in this context? There aren't any branches in unrolled loops after all.

>>7
>There aren't any branches in unrolled loops after all
I don't think you really understand loop unrolling.

>>8
>There aren't any branches in unrolled loops after all
I don't think you really understand loop unrolling.
I don't think you really understand either ^{loop unrolling} or _quoting.

I don't think >>5-8 understand ^_trolling.

and BOOK He DRAGON  i FORTRON It's doing the banned.  was  (to think In would it think which