Add proper compile pipeline #33
Merged
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
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.
This PR adds a compilation pipeline similar to Pluthon and Opshin. However this is more a glorified way of applying optimizations. Consistent with Opshin and Pluthon optimizations can be turned on and off using command line flags.
This also introduces two optimizations, a remover of Trace operations (which is an O3 optimization as it changes semantics) and a remover of Force(Delay(x)) constructs that have no semantic effect.
Moreover this closes #26 with a restricted (and thus safer) version, that checks whether the evaluation result is a constant or similar value that can be safely constant folded.