Lines Matching refs:IR

17 ir.h for the IR structures.
35 7) The driver performs code generation out of the IR, taking a linked
37 ir_to_mesa.cpp for Mesa IR code generation.
41 Q: What is HIR versus IR versus LIR?
44 high-level IR ("HIR"), with things like matrix operations, structure
49 producing a low level IR ("LIR").
54 accesses, and matrix multiplication broken down.  The Mesa IR backend
57 shader IR backend could potentially even handle some matrix operations
58 without breaking them down, but the 965 fragment shader IR backend
61 low-level IR that will make everyone happy.  So that usage has fallen
66 Q: How is the IR structured?
97 ir_instruction instance may only appear once in the whole IR tree with
129 A: Converting an IR tree to SSA form makes dead code elmimination,
152 IR backend, SSA does not appear to be that important to producing
160 in many cases you'll want to do a pass over the IR to convert
163 Mesa IR (and many hardware backends) only have a reciprocal
168 Q: How shoud I handle my special hardware instructions with respect to IR?
172 the IR.  Generally this is in the form of an ir_{bin,un}op expression
190 would rather see it), or scan the IR and convert to use your new
206 For IR transformations, a temporary context is used, then at the end
208 shader's IR list, and the old context full of dead nodes is freed.
209 When developing a single IR transformation pass, this means that you
213 so they find it by calling talloc_parent() on a nearby IR node.  The