Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure 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
  • DynamoRIO
  • dynamorio
  • Issues
  • #3821
Closed
Open
Issue created Sep 09, 2019 by Hendrik Greving@hgreving2304Contributor

drreg losing track of spilled registers when called outside of insertion phase.

When using drreg outside of the insertion phase, it defaults to a forward scan of the ilist to determine register liveness. At the beginning of the function drreg_forward_analysis, it flat-rate sets ever_spilled to false for each register. So if you call drreg_reserve_register() more than once, the ever_spilled of the first is false again. As a consequence, registers except the one of the last call of drreg_reserve_register() are never restored.

Assignee
Assign to
Time tracking