forked from llvm/llvm-project
-
Notifications
You must be signed in to change notification settings - Fork 3
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
FXML.1923: PDLL support for native constraints with attribute results #24
Merged
martin-luecke
merged 12 commits into
feature/fused-ops
from
origin/martin.FXML-1923.PDL_native_constraint_with_results
Apr 26, 2023
Merged
Changes from 8 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
dbcc0d0
Add PDLL parsing support for native constraints with results
martin-luecke 752a4c5
Add PDL support for representing native constraints with results
martin-luecke 4e7b37c
Add PDL_interp support for representing native constraints with results
martin-luecke c082d54
Add test for pdl_interp.apply_constraint with results
martin-luecke a238ae9
change pdl.apply_native_constraint printing format
martin-luecke ca0d7d7
PDLToPDLInterpPass: Add support for native constraints with results
martin-luecke bea4b57
PDL Bytecode generator + interpreter: Added support for constraints w…
martin-luecke 5b4fa7b
Fix for constraints with unused results
martin-luecke 050190d
Add registry specific to native constraints with results
martin-luecke 8f3c881
Adjust assert message for unregistered constraints
martin-luecke 9b32727
constrain the allowed type of constraint functions with results
martin-luecke b98b75e
adjust comments
martin-luecke 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 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 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 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 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 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 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 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 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 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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know enough about
PDLInterp
, could you give me an example when this is relevant?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my description on top:
An example for the output of this pass is the following:
PDL input:
The PDL_interp output is the following:
The
pdl_interp.record_match
operation and the block it is in is not the last thing this pass generates for a matcher. This is done so the operation that is the last check before a successful match can have this block (^bb4) as successor (e.g.%0 = pdl_interp.apply_constraint
here). But thepdl_interp.record_match
needs the result of%0 = pdl_interp.apply_constraint
as operand.So there is a cyclic dependency here, which we solve using the placeholder.
In short:
%0 = pdl_interp.apply_constraint
needs the success branch as successor.pdl_interp.record_match
is created with the success branch and needs the result%0
as operand