llvm-project/mlir/lib/TableGen/Pass.cpp

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

100 lines
3.1 KiB
C++
Raw Normal View History

//===- Pass.cpp - Pass related classes ------------------------------------===//
//
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
// See https://llvm.org/LICENSE.txt for license information.
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
//
//===----------------------------------------------------------------------===//
#include "mlir/TableGen/Pass.h"
#include "llvm/TableGen/Record.h"
using namespace mlir;
using namespace mlir::tblgen;
//===----------------------------------------------------------------------===//
// PassOption
//===----------------------------------------------------------------------===//
StringRef PassOption::getCppVariableName() const {
return def->getValueAsString("cppName");
}
StringRef PassOption::getArgument() const {
return def->getValueAsString("argument");
}
StringRef PassOption::getType() const { return def->getValueAsString("type"); }
Optional<StringRef> PassOption::getDefaultValue() const {
StringRef defaultVal = def->getValueAsString("defaultValue");
return defaultVal.empty() ? Optional<StringRef>() : defaultVal;
}
StringRef PassOption::getDescription() const {
return def->getValueAsString("description");
}
Optional<StringRef> PassOption::getAdditionalFlags() const {
StringRef additionalFlags = def->getValueAsString("additionalOptFlags");
return additionalFlags.empty() ? Optional<StringRef>() : additionalFlags;
}
bool PassOption::isListOption() const {
return def->isSubClassOf("ListOption");
}
//===----------------------------------------------------------------------===//
// PassStatistic
//===----------------------------------------------------------------------===//
StringRef PassStatistic::getCppVariableName() const {
return def->getValueAsString("cppName");
}
StringRef PassStatistic::getName() const {
return def->getValueAsString("name");
}
StringRef PassStatistic::getDescription() const {
return def->getValueAsString("description");
}
//===----------------------------------------------------------------------===//
// Pass
//===----------------------------------------------------------------------===//
Pass::Pass(const llvm::Record *def) : def(def) {
for (auto *init : def->getValueAsListOfDefs("options"))
options.emplace_back(init);
for (auto *init : def->getValueAsListOfDefs("statistics"))
statistics.emplace_back(init);
Separate the Registration from Loading dialects in the Context This changes the behavior of constructing MLIRContext to no longer load globally registered dialects on construction. Instead Dialects are only loaded explicitly on demand: - the Parser is lazily loading Dialects in the context as it encounters them during parsing. This is the only purpose for registering dialects and not load them in the context. - Passes are expected to declare the dialects they will create entity from (Operations, Attributes, or Types), and the PassManager is loading Dialects into the Context when starting a pipeline. This changes simplifies the configuration of the registration: a compiler only need to load the dialect for the IR it will emit, and the optimizer is self-contained and load the required Dialects. For example in the Toy tutorial, the compiler only needs to load the Toy dialect in the Context, all the others (linalg, affine, std, LLVM, ...) are automatically loaded depending on the optimization pipeline enabled. To adjust to this change, stop using the existing dialect registration: the global registry will be removed soon. 1) For passes, you need to override the method: virtual void getDependentDialects(DialectRegistry &registry) const {} and registery on the provided registry any dialect that this pass can produce. Passes defined in TableGen can provide this list in the dependentDialects list field. 2) For dialects, on construction you can register dependent dialects using the provided MLIRContext: `context.getOrLoadDialect<DialectName>()` This is useful if a dialect may canonicalize or have interfaces involving another dialect. 3) For loading IR, dialect that can be in the input file must be explicitly registered with the context. `MlirOptMain()` is taking an explicit registry for this purpose. See how the standalone-opt.cpp example is setup: mlir::DialectRegistry registry; registry.insert<mlir::standalone::StandaloneDialect>(); registry.insert<mlir::StandardOpsDialect>(); Only operations from these two dialects can be in the input file. To include all of the dialects in MLIR Core, you can populate the registry this way: mlir::registerAllDialects(registry); 4) For `mlir-translate` callback, as well as frontend, Dialects can be loaded in the context before emitting the IR: context.getOrLoadDialect<ToyDialect>() Differential Revision: https://reviews.llvm.org/D85622
2020-08-19 04:01:19 +08:00
for (StringRef dialect : def->getValueAsListOfStrings("dependentDialects"))
dependentDialects.push_back(dialect);
}
StringRef Pass::getArgument() const {
return def->getValueAsString("argument");
}
StringRef Pass::getBaseClass() const {
return def->getValueAsString("baseClass");
}
StringRef Pass::getSummary() const { return def->getValueAsString("summary"); }
StringRef Pass::getDescription() const {
return def->getValueAsString("description");
}
StringRef Pass::getConstructor() const {
return def->getValueAsString("constructor");
}
Separate the Registration from Loading dialects in the Context This changes the behavior of constructing MLIRContext to no longer load globally registered dialects on construction. Instead Dialects are only loaded explicitly on demand: - the Parser is lazily loading Dialects in the context as it encounters them during parsing. This is the only purpose for registering dialects and not load them in the context. - Passes are expected to declare the dialects they will create entity from (Operations, Attributes, or Types), and the PassManager is loading Dialects into the Context when starting a pipeline. This changes simplifies the configuration of the registration: a compiler only need to load the dialect for the IR it will emit, and the optimizer is self-contained and load the required Dialects. For example in the Toy tutorial, the compiler only needs to load the Toy dialect in the Context, all the others (linalg, affine, std, LLVM, ...) are automatically loaded depending on the optimization pipeline enabled. To adjust to this change, stop using the existing dialect registration: the global registry will be removed soon. 1) For passes, you need to override the method: virtual void getDependentDialects(DialectRegistry &registry) const {} and registery on the provided registry any dialect that this pass can produce. Passes defined in TableGen can provide this list in the dependentDialects list field. 2) For dialects, on construction you can register dependent dialects using the provided MLIRContext: `context.getOrLoadDialect<DialectName>()` This is useful if a dialect may canonicalize or have interfaces involving another dialect. 3) For loading IR, dialect that can be in the input file must be explicitly registered with the context. `MlirOptMain()` is taking an explicit registry for this purpose. See how the standalone-opt.cpp example is setup: mlir::DialectRegistry registry; registry.insert<mlir::standalone::StandaloneDialect>(); registry.insert<mlir::StandardOpsDialect>(); Only operations from these two dialects can be in the input file. To include all of the dialects in MLIR Core, you can populate the registry this way: mlir::registerAllDialects(registry); 4) For `mlir-translate` callback, as well as frontend, Dialects can be loaded in the context before emitting the IR: context.getOrLoadDialect<ToyDialect>() Differential Revision: https://reviews.llvm.org/D85622
2020-08-19 04:01:19 +08:00
ArrayRef<StringRef> Pass::getDependentDialects() const {
return dependentDialects;
}
ArrayRef<PassOption> Pass::getOptions() const { return options; }
ArrayRef<PassStatistic> Pass::getStatistics() const { return statistics; }