Lines Matching refs:bufferize

1 // RUN: mlir-opt %s -one-shot-bufferize="allow-return-allocs-from-loops bufferize-function-boundari…
2 // RUN: mlir-opt %s -one-shot-bufferize="allow-return-allocs-from-loops bufferize-function-boundari…
5 // RUN: mlir-opt %s -one-shot-bufferize="allow-return-allocs-from-loops bufferize-function-boundari…
6 // RUN: mlir-opt %s -one-shot-bufferize="allow-return-allocs-from-loops bufferize-function-boundari…
7 // RUN: mlir-opt %s -one-shot-bufferize="allow-return-allocs-from-loops bufferize-function-boundari…
505     // TODO: This one could bufferize inplace, but the analysis is too restrictive.
541   // Read the old value of %t1. Forces the transfer_write to bufferize
607 // This is a regression test. Everything can bufferize in-place because %7 and
709     // Must bufferize out-of-place because definition of read is in a different
732     // Can bufferize in-place.
746   // Cannot bufferize in-place according to normal op dominance rules.
768     // No further read of %0, so this can bufferize in-place.
784   // Cannot bufferize in-place according to normal op dominance rules.
814     // linalg.fill must bufferize out-of-place because every thread needs a
816     // can bufferize in place.
846     // linalg.fill must bufferize out-of-place because every thread needs a
848     // can bufferize in place.
873     // linalg.fill must bufferize out-of-place because every thread needs a
875     // can bufferize in place.
903     // linalg.fill can bufferize in-place because no alias of %alloc1 is read.