Hydro code analysis ideas

[jmeaster30]

• [ ] track module and function dependencies
  • [ ] find functions that will never be used
  • [ ] find modules that will never be used
  • [ ] write a minified that will take an input and produce a minified output
  • [ ] allow for querying in debugger for questions such as
    • [ ] where is this function called between x instruction and y instruction (including calls in further functions)
    • [ ] what functions call this function
  • [ ] output dependency graph for visualization
• [ ] check for stack overflows and underflows
• [ ] type checking / undefined reference checking
• [ ] possible value checking
  • [ ] ability to query "what values of x variable are possible at this given point"
• [ ] adding a gui for the analyzer and debugger would be really nice for visualizations and easier workflows over the cli

[jmeaster30]

Need an analysis graph type structure that encodes control flow

Each node will carry a bunch of info:

• Instruction (necessary to figure out the other pieces of info)
• Stack size
• Possible values of variables
• Allocation of variables

I think there is going to be some tricky parts with but we will see!