[WIP] automatic control flow #1754
Open
+3,018
−978
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.
Automatic Control Flow handling. Support different kinds of If/For to pass Polybench testsuite.
Modify Julia Middle-End (type inference and optimizer) to detect and apply control flow handling.
Use GPUCompiler Interpreter with a custom ORC JIT to bypass OpaqueClosure.
WIP integration with Reactant, missing mostly ways to control these analysis (type inference can be heavy because of inference reset). Missing a lot of comments / cleanup / tests integration.
Missing part (mostly not needed for Polybench):
f(A) = for i in 1:64 A[i] = Traced end)