summaryrefslogtreecommitdiffstats
path: root/mlir/lib/Transforms/LoopTiling.cpp
diff options
context:
space:
mode:
authorNicolas Vasilache <ntv@google.com>2019-09-27 09:55:38 -0700
committerA. Unique TensorFlower <gardener@tensorflow.org>2019-09-27 09:57:36 -0700
commitddf737c5da728f25c5e0413bc737d04b2d92df96 (patch)
tree07af0e3ba0f3755d11d329ccde15e8479ca04cd7 /mlir/lib/Transforms/LoopTiling.cpp
parent6543e99fe51b9077d8185ba9741770adc5f7cde5 (diff)
downloadbcm5719-llvm-ddf737c5da728f25c5e0413bc737d04b2d92df96.tar.gz
bcm5719-llvm-ddf737c5da728f25c5e0413bc737d04b2d92df96.zip
Promote MemRefDescriptor to a pointer to struct when passing function boundaries in LLVMLowering.
The strided MemRef RFC discusses a normalized descriptor and interaction with library calls (https://groups.google.com/a/tensorflow.org/forum/#!topic/mlir/MaL8m2nXuio). Lowering of nested LLVM structs as value types does not play nicely with externally compiled C/C++ functions due to ABI issues. Solving the ABI problem generally is a very complex problem and most likely involves taking a dependence on clang that we do not want atm. A simple workaround is to pass pointers to memref descriptors at function boundaries, which this CL implement. PiperOrigin-RevId: 271591708
Diffstat (limited to 'mlir/lib/Transforms/LoopTiling.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud