-
Notifications
You must be signed in to change notification settings - Fork 25
[water] NormalForm Module #657
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
base: main
Are you sure you want to change the base?
Conversation
ftynse
left a comment
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.
Not for this PR, but we will likely want this op in a separate dialect, working towards generalization of normal forms.
cc @fabianmcg
|
Nice! Thanks @ftynse for the pointer! We realized we couldn't continue without some version of them, so we also took a stab at implementing them. Putting here our relevant files. We should likely sync at some point.
I used |
b6a58bd to
06e7dba
Compare
| if (emitRemark) | ||
| return mlir::emitRemark(loc); | ||
|
|
||
| return mlir::emitError(loc); |
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.
pass nullstream if we don't want errors. Remarks should already not be emitted by default??? Or call abandon on inflight diagnostic
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.
IDK if we can create an InFlightDiagnostic that will not actually emit anything if so, we can try that. Otherwise, we can (rather heavily) have a wrapper class that holds an optional InFlightDiagnostic and has the same API so it's transparent to the caller. Another heavy-ish solution is to register a diagnostic handler that discards all errors before the interface method call and unregister it immediately after, though we may potentially discard some errors that are not specific to the interface method.
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.
It seems like we can just abandon the diagnostic before returning it to the verifier.
8219fb4 to
58a9d7e
Compare
The talk was more of an overall vision, we don't have to implement all of that. The dependencies between verifiers are a nice idea. What I also want here is a way to control error emission, so we can "discover" which forms are present without reporting errors, for example. |
Signed-off-by: Tim Gymnich <[email protected]>
Signed-off-by: Tim Gymnich <[email protected]>
Signed-off-by: Tim Gymnich <[email protected]>
Signed-off-by: Tim Gymnich <[email protected]>
Signed-off-by: Tim Gymnich <[email protected]>
e3c6e37 to
21c2c40
Compare
Uh oh!
There was an error while loading. Please reload this page.