Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • asm asm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • asmasm
  • asmasm
  • Merge requests
  • !179

Multiple methods for initializing analysis values

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Jason Zaugg requested to merge retronymm/asm:unfork/new-value into master Jun 11, 2018
  • Overview 7
  • Commits 2
  • Pipelines 5
  • Changes 3

Introduces a number of methods that are called when initializing or updating abstract values in an analyzer frame.

Before this commit, Analyzer.analyze and Frame.execute would always call Interpreter.newValue for initializing or updating frame values.

Having multiple methods allows users to return more precise values for the individual cases. For example, in a nullness analysis, the initial value for the this parameter of an instance method can be set to not-null.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: unfork/new-value