Lines Matching refs:allocation

32 in the following consecutive order: allocation, write-buffer, read- buffer. In
63 manageable allocation operations that implement the `SideEffects` interface.
90 can detect and handle the different allocation types that might be intermixed.
92 Note: the current version does not support allocation operations returning
168 The following example demonstrates an allocation using dynamically shaped types.
169 Due to the data dependency of the allocation to %0, we cannot move the
170 allocation out of bb2 in this case:
195 pay attention to the control flow and all potential aliases a buffer allocation
255 properly. Note further that the unnecessary allocation of %3 can be easily
263 encounter an alias that is not properly dominated by our allocation, we mark
412     %3 = memref.alloc(%arg0, %arg1) : memref<?x?xf32>  // nested allocation in a div.
448 above that uses a nested allocation:
468 Since the allocation %2 happens in a divergent branch and cannot be safely
523                                     // divergent allocation
539 Since this allocation happens in the scope of a divergent branch, %2 becomes a
620 target. The unused allocation and deallocation operations that are defined for