Repository navigation
Refactor analysis - #119
Merged
Merged
Conversation
…into dataflow_analysis
… analog type checker to assume definite assignment analysis. Add test cases for analog definite assignment analysis.
…and test_analysis_analog for bounds checker.
…matching of modes, qubits and hamitlonian to a different analysis
…ttom, rename SUPPORTED_FUNC_SIGNATURES in analog to ANALOG_SUPPORTED_FUNC_SIGNATURES
… modified get_type_name
…d default analyze method
…stent dimensions for operators and targets
…ed edge labels for CFG
…oming from lattice instead of DataflowAnalysis base class
…at has the false branch of the while loop in its postdominance
…ign/oqd-core into dataflow_analysis
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
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Refactor: Modify analog analysis for updated dataflow analysis in oqd-compiler-infrastructure.
Features Implemented:
What is the current behavior? (You can also link to an open issue here)
Analog analysis implementation is sub-optimal and incomplete.
What is the new behavior (if this is a feature change)?
Clean implementation of analog analysis. Additional analysis as listed above.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Yes. Analysis is run by calling the
analyzemethod, which takes the CFG as a parameter.Other information:
N/A