Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Register
  • Sign in
  • CPAchecker CPAchecker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 410
    • Issues 410
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SoSy-LabSoSy-Lab
  • Software
  • CPAcheckerCPAchecker
  • Issues
  • #398
Closed
Open
Issue created Jul 13, 2018 by 🤖 SoSy-Bot 🤖@sosy-botOwner

Value Analysis could use ambiguous Pointers in PointerCPA strengthening

Original issue created by @lemberger on 2018-05-14 at 15:49:34, last modified on 2018-05-14 at 15:49:34


Currently, the value analysis uses information from the PointerCPA about a pointer only, if the pointer can only point to exactly one address. We could improve this so that the value analysis also uses information, if a pointer could point a) to multiple locations or b) to any location.

In the first case, this could significantly increase the state space, though.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking