Lines Matching full:operations

18 operations, types, and attributes.
41 	which can be packaged neatly with the `acc` dialect operations.
60 	operations, like data operations, are expected to generate results
69 	In order for the operations in the `acc` dialect to be optimizable
74 are adhered to. Current and planned operations, attributes, types must
79 The OpenACC dialect includes both high-level operations (which retain
81 intermediate-level operations (which are used to decompose clauses
82 from constructs), and low-level operations (to encode specifics
85 The high-level operations list contains the following OpenACC language
86 constructs and their corresponding operations:
105 This second group contains operations which are used to represent
140 The low-level operations are:
148 The low-level operations semantics and reasoning are further explained
151 ### Data Operations
162 * Operations can be moved or optimized individually (eg `CSE`).
169 * Clear operation ordering since all data operations are on same
172 Each of the `acc` dialect data operations represents either the
181 The `acc` data operations, even when decomposed, retain their original
185 for entry and `acc.copyout` for exit. Both the decomposed operations
188 The link between the decomposed entry and exit operations is the ssa
205 `acc.bounds` operations.
242 The data operations also maintain semantics described in the OpenACC
283 Data clause operations (eg. `acc.copyin`) rely on the following type
297 * type of result of acc data clause operations
312 	operations. These are synthetic types solely used for proper IR
336 of data clause operations (eg. `acc.copyin`). They are as follows:
413 are represented through multiple operations and attributes:
438 operations producing globals and on operations producing locals such as
441 `acc.declare*` operations.
471 dialect operations must be valid when constructed:
512 The data operations are modeled in a way where data entry operations
513 look like loads and data exit operations look like stores. Thus these
514 operations are intended to be optimized in the following ways:
515 * Be able to eliminate redundant operations such as when an `acc.copyin`
517 * Be able to hoist/sink such operations out of loops.
519 ## Operations TOC