-
Updated
Apr 11, 2022 - C++
mlir
Here are 33 public repositories matching this topic...
The existing code assumes the result tensor type is the same as input type for a few aten ops like log, exp, erf. See https://github.com/llvm/torch-mlir/blob/486f95e84f587d020ba789b071b12f890510f1a1/lib/Dialect/Torch/Transforms/RefineTypes.cpp#L221-L235
This incorrect. The result tensor of these ops should always have the default dtype rather than the same as the input type. E2E tests fo
-
Updated
Mar 24, 2022 - C++
In test/create-cores/test_dma1.mlir, -aie-lower-memcpy convert
AIE.memcpy @token0(1, 2) (%t11 : <%buf0, 0, 256>, %t22 : <%buf1, 0, 256>) : (memref<256xi32>, memref<256xi32>)
AIE.memcpy @token1(1, 2) (%t11 : <%buf0, 0, 256>, %t33 : <%buf2, 0, 256>) : (memref<256xi32>, memref<256xi32>)
to (only shows the %t11 side)
%2 = AIE.mem(%0) {
%15 = AIE.dmaStart(MM2S0, ^bb1
-
Updated
Aug 30, 2021 - C++
-
Updated
Feb 20, 2022 - C++
-
Updated
Dec 23, 2021 - Python
Improve this page
Add a description, image, and links to the mlir topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mlir topic, visit your repo's landing page and select "manage topics."
Currently, Grand Central will output multiline YAML description strings as one line, e.g.,
"foo\nbar\baz". However, the LLVM YAML library has support for instead emitting this in "block scala" format: https://llvm.org/docs/YamlIO.html#block-scalars. Change FIRRTL's Grand Central pass to do block scalar output of description strings for better readability of the output YAML.Once implemented,