diff options
| author | Nicolas Vasilache <ntv@google.com> | 2019-05-03 11:07:37 -0700 |
|---|---|---|
| committer | Mehdi Amini <joker.eph@gmail.com> | 2019-05-06 08:26:44 -0700 |
| commit | 258e8d9ce2e7da290dbda335771d5e84e04c813a (patch) | |
| tree | 0ef45f058d85a2ee9955af5f94557127813e93bb /mlir/lib/Transforms/MaterializeVectors.cpp | |
| parent | ff6e7cf558135055f65202f73a0c06db7a53e77d (diff) | |
| download | bcm5719-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/MaterializeVectors.cpp')
| -rw-r--r-- | mlir/lib/Transforms/MaterializeVectors.cpp | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/mlir/lib/Transforms/MaterializeVectors.cpp b/mlir/lib/Transforms/MaterializeVectors.cpp index 76dbdafb08d..2f06a9aa3bf 100644 --- a/mlir/lib/Transforms/MaterializeVectors.cpp +++ b/mlir/lib/Transforms/MaterializeVectors.cpp @@ -772,7 +772,8 @@ mlir::createMaterializeVectorsPass(llvm::ArrayRef<int64_t> vectorSize) { } static PassRegistration<MaterializeVectorsPass> - pass("materialize-vectors", "Materializes super-vectors to vectors of the " - "proper size for the hardware"); + pass("affine-materialize-vectors", + "Materializes super-vectors to vectors of the " + "proper size for the hardware"); #undef DEBUG_TYPE |
