Lines Matching refs:simplified

1 # MLIR: The case for a simplified polyhedral form
10 that explored the tradeoffs of using this simplified form vs the traditional
180 the simplified form, we also have an "if" instruction that takes an affine
228 out after code generation. With the simplified form, transformations have to do
273 its loops. The simplified form pays for this by eliminating schedules and
276 simplified form supports instruction duplication.
286 required as part of lowering to the target machine. The simplified form has a
302 In practice, the simplified form requires moving the complexity of code
316 The simplified form is much easier for analyses and transformations to build
336 The simplified form defines this away: the concepts in the IR remain simple, and
344 they are defined based on traditional dominance. In the simplified form, this is
394 In the simplified form, the effect of "code generation" is always obvious from
400 One hybrid alternative is to support both the traditional and simplified forms
406 1.  Partial code generation lowers to the simplified form