Require dual C and MLIR verification - #2
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Make backend portability an executable contract for
flow-idiomatics, not a documentation claim.The same seven portable flagship programs must:
mlir-opt;The stricter gate immediately exposed genuine compiler parity gaps (spans/slices, match binding/wildcards/guards/termination, and first-class/capturing closures), which were fixed in Flow PR #730 rather than by simplifying these programs.
Flow #730 is now merged. The temporary compiler SHA pin has been removed and this PR is rerunning the exact C/MLIR/benchmark matrix against current Flow
mainbefore merge.