Add translation layer from pattern matching exceptions #4069
Conversation
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
Baltoli
added
the
merge-to-dependency-job
tothtamas28
approved these changes
Mar 1, 2024
|
Merged into and superseded by: #4071 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to: runtimeverification/llvm-backend#999
We are working on removing the backwards dependency from the LLVM backend to K; as part of that change we are removing usages of the frontend error handling mechanisms from the backend: runtimeverification/llvm-backend#1001
Doing so requires that we implement a translation layer from the new error types in runtimeverification/llvm-backend#1001 to the frontend infrastructure; by doing so we can recover the frontend's original behaviour in response to errors / warnings thrown or created during pattern matching.
This PR can be reviewed as-is in combination with the backend PR above; I will take care of the required lockstep merging to get both changes landed to the frontend together.