llvm-project/mlir/test/lib/Transforms/TestDataLayoutQuery.cpp
Alex Zinenko 3ba14fa0ce [mlir] Introduce data layout modeling subsystem
Data layout information allows to answer questions about the size and alignment
properties of a type. It enables, among others, the generation of various
linear memory addressing schemes for containers of abstract types and deeper
reasoning about vectors. This introduces the subsystem for modeling data
layouts in MLIR.

The data layout subsystem is designed to scale to MLIR's open type and
operation system. At the top level, it consists of attribute interfaces that
can be implemented by concrete data layout specifications; type interfaces that
should be implemented by types subject to data layout; operation interfaces
that must be implemented by operations that can serve as data layout scopes
(e.g., modules); and dialect interfaces for data layout properties unrelated to
specific types. Built-in types are handled specially to decrease the overall
query cost.

A concrete default implementation of these interfaces is provided in the new
Target dialect. Defaults for built-in types that match the current behavior are
also provided.

Reviewed By: rriddle

Differential Revision: https://reviews.llvm.org/D97067
2021-03-11 16:54:47 +01:00

61 lines
2.1 KiB
C++

//===- TestDataLayoutQuery.cpp - Test Data Layout Queries -----------------===//
//
// 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 "TestDialect.h"
#include "mlir/Dialect/DLTI/DLTI.h"
#include "mlir/IR/BuiltinAttributes.h"
#include "mlir/Pass/Pass.h"
using namespace mlir;
namespace {
/// A pass that finds "test.data_layout_query" operations and attaches to them
/// attributes containing the results of data layout queries for operation
/// result types.
struct TestDataLayoutQuery
: public PassWrapper<TestDataLayoutQuery, FunctionPass> {
void runOnFunction() override {
FuncOp func = getFunction();
Builder builder(func.getContext());
DenseMap<Operation *, DataLayout> layouts;
func.walk([&](test::DataLayoutQueryOp op) {
// Skip the ops with already processed in a deeper call.
if (op->getAttr("size"))
return;
auto scope = op->getParentOfType<test::OpWithDataLayoutOp>();
if (!layouts.count(scope)) {
layouts.try_emplace(
scope, scope ? cast<DataLayoutOpInterface>(scope.getOperation())
: nullptr);
}
const DataLayout &layout = layouts.find(scope)->getSecond();
unsigned size = layout.getTypeSize(op.getType());
unsigned alignment = layout.getTypeABIAlignment(op.getType());
unsigned preferred = layout.getTypePreferredAlignment(op.getType());
op->setAttrs(
{builder.getNamedAttr("size", builder.getIndexAttr(size)),
builder.getNamedAttr("alignment", builder.getIndexAttr(alignment)),
builder.getNamedAttr("preferred", builder.getIndexAttr(preferred))});
});
}
};
} // namespace
namespace mlir {
namespace test {
void registerTestDataLayoutQuery() {
PassRegistration<TestDataLayoutQuery>("test-data-layout-query",
"Test data layout queries");
}
} // namespace test
} // namespace mlir