How to help the compiler eliminate loops and arrays?

Unrolling loops does have a disadvantage: It makes the code bigger. Bigger code means more memory accesses to fetch the code, and since memory access is slow, your code could end up being slower. Also, the Intel cpus preprocess the fetched code and turn them into uOps (micro ops) which are then scheduled and executed.

The CPU has a cache of these uOps so it only decodes instructions that aren't already in the cache. So, an unrolled loop will fill up the cache and cause other code to bumped out. Smaller code is generally better As for arrays, I'm not sure how you'd get rid of them So, if you had: struct TextureUnit { // some texture unit data } TextureUnit units number_of_units; for (int I = 0 ; I someparams); } but you'd need to see what the compiler is generating in the optimised build to be sure it actually gives any advantages I think this might be classed as a 'micro-optimisation', so I wouldn't really be worried about it unless you can prove it really is a bottleneck.

Remember - profile the code, don't just guess.

Unrolling loops does have a disadvantage: It makes the code bigger. Bigger code means more memory accesses to fetch the code, and since memory access is slow, your code could end up being slower. Also, the Intel cpus preprocess the fetched code and turn them into uOps (micro ops) which are then scheduled and executed.

The CPU has a cache of these uOps so it only decodes instructions that aren't already in the cache. So, an unrolled loop will fill up the cache and cause other code to bumped out. Smaller code is generally better.

As for arrays, I'm not sure how you'd get rid of them. So, if you had: struct TextureUnit { // some texture unit data } TextureUnit units number_of_units; for (int I = 0 ; I someparams); } but you'd need to see what the compiler is generating in the optimised build to be sure it actually gives any advantages. I think this might be classed as a 'micro-optimisation', so I wouldn't really be worried about it unless you can prove it really is a bottleneck.

Remember - profile the code, don't just guess.

I don't know much about computer graphics, but this trivial test shows that for TEXTURE_COUNT=1 and -O1 g++ doesn't branch. I suspect this will extend even for many real life programs, but why don't you try for yourself. Use -S to see the generated assembly.

#include typedef struct fake_texture { int r, g, b; } texture; int main() { texture arrayTEXTURE_COUNT = {}; for(int I = 0; I B += 3; } for(int I = 0; I Cfi_startproc . Cfi_personality 0x0,__gxx_personality_v0 pushl %ebp . Cfi_def_cfa_offset 8 movl %esp, %ebp .

Cfi_offset 5, -8 . Cfi_def_cfa_register 5 andl $-16, %esp subl $32, %esp movl $1, 20(%esp) movl $2, 24(%esp) movl $3, 28(%esp) movl $1, 8(%esp) movl $. LC0, 4(%esp) movl $1, (%esp) call __printf_chk movl $0, %eax leave ret .

Cfi_endproc.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.