summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/r300/compiler/radeon_emulate_loops.c
AgeCommit message (Collapse)Author
2010-07-03r300/compiler: Correctly calculate the max number of iterations for loops.Tom Stellard
2010-07-03r300/compiler: Handle loops in deadcode analysis.Tom Stellard
This also allows us to split the loop emulation into two phases. A tranformation phase which either unrolls loops or prepares them to be emulated, and the emulation phase which unrolls remaining loops until the instruction limit is reached. The second phase is completed after the deadcode analysis in order to get a more accurate count of the number of instructions in the body of loops.
2010-06-11r300/compiler: Handle more complex conditionals in loops.Tom Stellard
2010-06-11r300/compiler: Fix warning.Tom Stellard
2010-06-11r300/compiler: Handle SGT and SLE at the beginning of loops.Tom Stellard
2010-06-11r300/compiler: Verify assumptions about opcode types.Tom Stellard
2010-06-11r300/compiler: Unroll loops that decrement the counter.Tom Stellard
e.g. for(i=10; i>0; i--)
2010-06-11r300/compiler: Unroll loops that have a constant number of iterations.Tom Stellard
This only works with for loops that increment the counter. e.g. for(i=0; i<10; i++)
2010-06-11r300/compiler: Implement simple loop emulationTom Stellard
The loop emulation unrolls loops as may times as possbile while still keeping the shader program below the maximum instruction limit. At this point, there are no checks for constant conditionals. This is only enabled for fragment shaders.