summaryrefslogtreecommitdiffstats
path: root/mlir/lib/Transforms/LoopTiling.cpp
diff options
context:
space:
mode:
authorNicolas Vasilache <ntv@google.com>2019-05-03 11:07:37 -0700
committerMehdi Amini <joker.eph@gmail.com>2019-05-06 08:26:44 -0700
commit258e8d9ce2e7da290dbda335771d5e84e04c813a (patch)
tree0ef45f058d85a2ee9955af5f94557127813e93bb /mlir/lib/Transforms/LoopTiling.cpp
parentff6e7cf558135055f65202f73a0c06db7a53e77d (diff)
downloadbcm5719-llvm-258e8d9ce2e7da290dbda335771d5e84e04c813a.tar.gz
bcm5719-llvm-258e8d9ce2e7da290dbda335771d5e84e04c813a.zip
Prepend an "affine-" prefix to Affine pass option names - NFC
Trying to activate both LLVM and MLIR passes in mlir-cpu-runner showed name collisions when registering pass names. One possible way of disambiguating that should also work across dialects is to prepend the dialect name to the passes that specifically operate on that dialect. With this CL, mlir-cpu-runner tests still run when both LLVM and MLIR passes are registered -- PiperOrigin-RevId: 246539917
Diffstat (limited to 'mlir/lib/Transforms/LoopTiling.cpp')
-rw-r--r--mlir/lib/Transforms/LoopTiling.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/mlir/lib/Transforms/LoopTiling.cpp b/mlir/lib/Transforms/LoopTiling.cpp
index 11f2468b1a9..4eb1ce22008 100644
--- a/mlir/lib/Transforms/LoopTiling.cpp
+++ b/mlir/lib/Transforms/LoopTiling.cpp
@@ -36,7 +36,7 @@
using namespace mlir;
-#define DEBUG_TYPE "loop-tile"
+#define DEBUG_TYPE "affine-loop-tile"
static llvm::cl::OptionCategory clOptionsCategory(DEBUG_TYPE " options");
@@ -413,4 +413,4 @@ void LoopTiling::runOnFunction() {
constexpr unsigned LoopTiling::kDefaultTileSize;
constexpr uint64_t LoopTiling::kDefaultCacheMemCapacity;
-static PassRegistration<LoopTiling> pass("loop-tile", "Tile loop nests");
+static PassRegistration<LoopTiling> pass("affine-loop-tile", "Tile loop nests");
OpenPOWER on IntegriCloud