Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design and implement flow analysis APIs #6895

Closed
ManishJayaswal opened this issue Nov 19, 2015 · 5 comments
Closed

Design and implement flow analysis APIs #6895

ManishJayaswal opened this issue Nov 19, 2015 · 5 comments
Labels
Area-Interactive Feature Request
Milestone
Backlog

Comments

@ManishJayaswal
Copy link
Contributor

No description provided.

@ManishJayaswal ManishJayaswal added this to the 1.2 milestone Nov 19, 2015
@ManishJayaswal ManishJayaswal mentioned this issue Nov 19, 2015
Open
31 tasks
@ManishJayaswal
Copy link
Contributor Author

@genlu

@ManishJayaswal ManishJayaswal modified the milestones: 1.3, 1.2 Jan 25, 2016
@ManishJayaswal ManishJayaswal modified the milestones: Unknown, 1.3 May 6, 2016
@ManishJayaswal
Copy link
Contributor Author

IOperation work is getting tracked via many other issues so closing this out.

@msJohnHamby
Copy link
Contributor

This is work on top of IOperation, and is not tracked by other issues.

@msJohnHamby msJohnHamby reopened this May 6, 2016
@ghost
Copy link

ghost commented Dec 26, 2016

Hey guys, do you want to extend the dataflow analysis functions that exist, or should we understand that there will be a new flow analysis api that does more job?
The existing data flow analysis functions gives us little information sometimes. If the result symbols are global variables (property or field) the AnalyzeDataFlow function returns a symbol "this" for every global varible. So we can not understand which varible is readinside for example.

@CyrusNajmabadi
Copy link
Member

Closing this out as we have AnalyzeDataFlow, and we have the new IOPeration and ControlFlowGraph apis to support these scenarios.

@CyrusNajmabadi CyrusNajmabadi closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Interactive Feature Request
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@CyrusNajmabadi @ManishJayaswal @msJohnHamby