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.
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
FXML.1923: PDLL support for native constraints with attribute results #24
Changes from 9 commits
dbcc0d0
752a4c5
4e7b37c
c082d54
a238ae9
ca0d7d7
bea4b57
5b4fa7b
050190d
8f3c881
9b32727
b98b75e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
How do we signal a
failure
with this interface? Don't we need something similar likeFailureOr<ResultT>
?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.
Good catch!
I think it makes sense to remove the template magic and under the hood conversion that is enabled by this. The problem is that not all valid native rewrite functions are also valid constraint with results functions. We would have to adjust how the conversion from PDL structures to built-in structure is done for this.
So for the scope of this PR we will only support constraints with results in form of
LogicalResult (PatternRewriter &, PDLResultList &, ArrayRef<PDLValue>)
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