-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[mlir] Add the ability to define dialect-specific location attrs. #105584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
bzcheeseman
merged 5 commits into
llvm:main
from
bzcheeseman:bzcheeseman/dialect-location-attrs
Oct 3, 2024
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
f5ceac4
[mlir] Add the ability to define dialect-specific location attrs.
bzcheeseman 3b5a1ba
Take suggestions from code review, and add a sanity-check test to ens…
bzcheeseman fa38aca
Forgot to delete this
bzcheeseman 2624e45
format
bzcheeseman 6823673
next round of comments
bzcheeseman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
//===- LocationTest.cpp - unit tests for affine map API -------------------===// | ||
// | ||
// 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/IR/Location.h" | ||
#include "mlir/IR/Builders.h" | ||
#include "gtest/gtest.h" | ||
|
||
using namespace mlir; | ||
|
||
// Check that we only walk *locations* and not non-location attributes. | ||
TEST(LocationTest, Walk) { | ||
MLIRContext ctx; | ||
Builder builder(&ctx); | ||
BoolAttr trueAttr = builder.getBoolAttr(true); | ||
|
||
Location loc1 = FileLineColLoc::get(builder.getStringAttr("foo"), 1, 2); | ||
Location loc2 = FileLineColLoc::get(builder.getStringAttr("foo"), 3, 4); | ||
Location fused = builder.getFusedLoc({loc1, loc2}, trueAttr); | ||
|
||
SmallVector<Attribute> visited; | ||
fused->walk([&](Location l) { | ||
visited.push_back(LocationAttr(l)); | ||
return WalkResult::advance(); | ||
}); | ||
|
||
EXPECT_EQ(llvm::ArrayRef(visited), ArrayRef<Attribute>({fused, loc1, loc2})); | ||
} | ||
|
||
// Check that we skip location attrs nested under a non-location attr. | ||
TEST(LocationTest, SkipNested) { | ||
MLIRContext ctx; | ||
Builder builder(&ctx); | ||
|
||
Location loc1 = FileLineColLoc::get(builder.getStringAttr("foo"), 1, 2); | ||
Location loc2 = FileLineColLoc::get(builder.getStringAttr("foo"), 3, 4); | ||
Location loc3 = FileLineColLoc::get(builder.getStringAttr("bar"), 1, 2); | ||
Location loc4 = FileLineColLoc::get(builder.getStringAttr("bar"), 3, 4); | ||
ArrayAttr arr = builder.getArrayAttr({loc3, loc4}); | ||
Location fused = builder.getFusedLoc({loc1, loc2}, arr); | ||
|
||
SmallVector<Attribute> visited; | ||
fused->walk([&](Location l) { | ||
visited.push_back(LocationAttr(l)); | ||
return WalkResult::advance(); | ||
}); | ||
|
||
EXPECT_EQ(llvm::ArrayRef(visited), ArrayRef<Attribute>({fused, loc1, loc2})); | ||
} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.