diff options
| author | Uday Bondhugula <uday@polymagelabs.com> | 2021-05-22 19:55:38 +0530 |
|---|---|---|
| committer | Uday Bondhugula <uday@polymagelabs.com> | 2021-05-24 08:43:10 +0530 |
| commit | 9c21ddb70ab56eb3ca5b0f99faa18bb3af17b3df (patch) | |
| tree | 93ecdc62e5dbf5a9310b45506a353ee8d65a028a /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
| parent | 000a05fd1ab33329f7ef2dd85a3f027a7d0c3a4b (diff) | |
[MLIR] Make MLIR cmake variable names consistent
Fix inconsistent MLIR CMake variable names. Consistently name them as
MLIR_ENABLE_<feature>.
Eg: MLIR_CUDA_RUNNER_ENABLED -> MLIR_ENABLE_CUDA_RUNNER
MLIR follows (or has mostly followed) the convention of naming
cmake enabling variables in the from MLIR_ENABLE_... etc. Using a
convention here is easy and also important for convenience. A counter
pattern was started with variables named MLIR_..._ENABLED. This led to a
sequence of related counter patterns: MLIR_CUDA_RUNNER_ENABLED,
MLIR_ROCM_RUNNER_ENABLED, etc.. From a naming standpoint, the imperative
form is more meaningful. Additional discussion at:
https://llvm.discourse.group/t/mlir-cmake-enable-variable-naming-convention/3520
Switch all inconsistent ones to the ENABLE form. Keep the couple of old
mappings needed until buildbot config is migrated.
Differential Revision: https://reviews.llvm.org/D102976
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions