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

[FEATURE REQUEST] Backward analysis (final version) #292

Open
lucaneg opened this issue Oct 6, 2023 · 0 comments
Open

[FEATURE REQUEST] Backward analysis (final version) #292

lucaneg opened this issue Oct 6, 2023 · 0 comments
Assignees
@lucaneg
Labels
❗ priority:p3 Priority planning - level 3 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🎆 type:feature New feature or request

Comments

@lucaneg
Copy link
Member

lucaneg commented Oct 6, 2023 •
edited
Loading

Description
As an extension and finalization of #120, we should:

  • swap the evaluation of sub-expressions with the outer-most one in NaryExpression and NaryStatement
  • provide a proper backward interproceduralAnalysis
  • provide a proper backward HeapDomain
  • provide a proper backward TypeDomain
  • investigate the need of a backward CallGraph
  • Support optimiziations (classes are there but results are unstable)
  • Thoroughly test the backward framework
@lucaneg lucaneg added 🎆 type:feature New feature or request ❗ priority:p3 Priority planning - level 3 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms labels Oct 6, 2023
@lucaneg lucaneg self-assigned this Oct 6, 2023
@lucaneg lucaneg added this to LiSA Oct 6, 2023
@lucaneg lucaneg moved this to Backlog in LiSA Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucaneg lucaneg

Labels
❗ priority:p3 Priority planning - level 3 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🎆 type:feature New feature or request
Projects
LiSA
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lucaneg