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] Customizable initialization of entrypoints parameters #280

Closed
lucaneg opened this issue Mar 20, 2023 · 0 comments · Fixed by #289
Closed

[FEATURE REQUEST] Customizable initialization of entrypoints parameters #280

lucaneg opened this issue Mar 20, 2023 · 0 comments · Fixed by #289
Assignees
@lucaneg
Labels
‼ priority:p1 Priority planning - level 1 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🎆 type:feature New feature or request
Milestone
0.1b9

Comments

@lucaneg
Copy link
Member

lucaneg commented Mar 20, 2023

Description
This could also be applied in general, in more places than entrypoint state initialization.

When creating the entry state for entrypoints, initialization of complex types (even just arrays) should be configurable depending on the language. For instance, Java arrays should allocated by also defining their length, as the semantics of the language might access it.
@lucaneg lucaneg added 🎆 type:feature New feature or request ‼ priority:p1 Priority planning - level 1 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs labels Mar 20, 2023
@lucaneg lucaneg added this to the 0.1b8 milestone Mar 20, 2023
@lucaneg lucaneg self-assigned this Mar 20, 2023
@lucaneg lucaneg added this to LiSA Mar 20, 2023
@lucaneg lucaneg moved this to Backlog in LiSA Mar 20, 2023
@lucaneg lucaneg moved this from Backlog to Todo in LiSA Apr 18, 2023
@lucaneg lucaneg modified the milestones: 0.1b8, 0.1 Apr 18, 2023
@lucaneg lucaneg moved this from Todo to Backlog in LiSA Apr 18, 2023
@lucaneg lucaneg added this to the 0.2 milestone Apr 20, 2023
@lucaneg lucaneg modified the milestones: 0.2, 0.1b9 Sep 9, 2023
@lucaneg lucaneg moved this from Backlog to Todo in LiSA Sep 9, 2023
@lucaneg lucaneg mentioned this issue Sep 11, 2023
Merged
@lucaneg lucaneg moved this from Todo to In Progress in LiSA Sep 28, 2023
lucaneg added a commit that referenced this issue Oct 2, 2023
@lucaneg
Default and unknown values at type level #280
217b756
@lucaneg lucaneg added the 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet label Oct 2, 2023
@lucaneg lucaneg moved this from In Progress to Done in LiSA Oct 2, 2023
@github-project-automation github-project-automation bot moved this from Done to Merged in LiSA Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lucaneg lucaneg

Labels
‼ priority:p1 Priority planning - level 1 🎊 resolution:resolved Bug or feature resolved - might not have been merged to master yet 🔍 scope:analysis Work regarding abstract domains or fixpoint algorithms 🌍 scope:interproc Work regarding interprocedural analyses or call graphs 🎆 type:feature New feature or request
Projects
LiSA
Archived in project
Milestone
0.1b9
Development

Successfully merging a pull request may close this issue.

Beta9 roundup lisa-analyzer/lisa
1 participant
@lucaneg